Techniques for configuring bandwidth parts and synchronization signal blocks

ABSTRACT

Methods, systems, and devices for wireless communications are described. A synchronization signal block (SSB) may be dynamically scheduled within an operating bandwidth of a user equipment (UE), where the operating bandwidth of the UE is outside of a frequency resource in which a cell defining SSB (CD-SSB) is scheduled. For example, a UE may operate in a reduced capability mode or an enhanced reduced capability mode where the UE may operate in a narrower bandwidth than the serving cell bandwidth. Control signaling may dynamically configure an SSB for the UE within the operating bandwidth of the UE. The UE may monitor for the non-cell defining SSB (NCD-SSB) and skip monitoring for the CD-SSB based on the dynamically configured NCD-SSB. For example, a reduced capability UE or an enhanced reduced capability UE may monitor for the NCD-SSB without performing RF retuning between receiving the control signaling and monitoring for the NCD-SSB.

TECHNICAL FIELD

The following relates to wireless communications, including configuringbandwidth parts and synchronization signal blocks.

BACKGROUND

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such asLong Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, orLTE-A Pro systems, and fifth generation (5G) systems which may bereferred to as New Radio (NR) systems. These systems may employtechnologies such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonalfrequency division multiplexing (DFT-S-OFDM). A wireless multiple-accesscommunications system may include one or more base stations, eachsupporting wireless communication for communication devices, which maybe known as user equipment (UE).

SUMMARY

The described techniques relate to improved methods, systems, devices,and apparatuses that support configuring bandwidth parts (BWPs) andsynchronization signal blocks (SSBs). For example, the describedtechniques provide for dynamic scheduling of an SSB within an operatingbandwidth of a user equipment (UE), where the operating bandwidth of theUE is outside of a frequency resource in which a cell defining SSB(CD-SSB) is scheduled for reception. For example, a UE may operate in areduced capability mode or an enhanced reduced capability mode in orderto save power. In a reduced capability mode or an enhanced reducedcapability mode, a UE may operate in a narrower bandwidth (e.g., a BWP)than the serving cell bandwidth. Control signaling may dynamicallyconfigure an SSB for the UE within the operating bandwidth of the UE. Areduced capability UE or an enhanced reduced capability UE may receive adownlink control information (DCI) or medium access control (MAC)control element (CE) that schedules or enables a non-cell defining SSB(NCD-SSB) that is within the UE's operating bandwidth. The UE maymonitor for the NCD-SSB in the indicated resource and skip monitoringfor the CD-SSB based on the dynamic indication of the resource for theNCD-SSB. For example, a reduced capability UE or an enhanced reducedcapability UE may monitor for the NCD-SSB without performing radiofrequency retuning between receiving the control signaling andmonitoring for the NCD-SSB. In some cases, the network entity mayschedule the NCD-SSB based on a latency target or a payload size ofcommunications with the UE.

A method for wireless communications at a UE is described. The methodmay include receiving control signaling, in an operating bandwidth ofthe UE, that schedules or enables a first SSB in a first resource of theoperating bandwidth of the UE, the first SSB being different from asecond SSB that is associated with system information of a cell thatoperates across a radio frequency bandwidth that includes the operatingbandwidth of the UE, where the second SSB is scheduled for receipt in asecond resource that is outside of the operating bandwidth of the UE andmonitoring, while still operating in the operating bandwidth of the UE,for the first SSB in the first resource based on the control signaling.

An apparatus for wireless communications at a UE is described. Theapparatus may include at least one processor, memory coupled with the atleast one processor, and instructions stored in the memory. Theinstructions may be executable by the at least one processor to causethe UE to receive control signaling, in an operating bandwidth of theUE, that schedules or enables a first SSB in a first resource of theoperating bandwidth of the UE, the first SSB being different from asecond SSB that is associated with system information of a cell thatoperates across a radio frequency bandwidth that includes the operatingbandwidth of the UE, where the second SSB is scheduled for receipt in asecond resource that is outside of the operating bandwidth of the UE andmonitor, while still operating in the operating bandwidth of the UE, forthe first SSB in the first resource based on the control signaling.

Another apparatus for wireless communications at a UE is described. Theapparatus may include means for receiving control signaling, in anoperating bandwidth of the UE, that schedules or enables a first SSB ina first resource of the operating bandwidth of the UE, the first SSBbeing different from a second SSB that is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, where the second SSB isscheduled for receipt in a second resource that is outside of theoperating bandwidth of the UE and means for monitoring, while stilloperating in the operating bandwidth of the UE, for the first SSB in thefirst resource based on the control signaling.

A non-transitory computer-readable medium storing code for wirelesscommunications at a UE is described. The code may include instructionsexecutable by at least one processor to receive control signaling, in anoperating bandwidth of the UE, that schedules or enables a first SSB ina first resource of the operating bandwidth of the UE, the first SSBbeing different from a second SSB that is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, where the second SSB isscheduled for receipt in a second resource that is outside of theoperating bandwidth of the UE and monitor, while still operating in theoperating bandwidth of the UE, for the first SSB in the first resourcebased on the control signaling.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving the first SSBwithout performing radio frequency retuning between receiving thecontrol signaling and monitoring for the first SSB.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for monitoring, prior toreceiving the control signaling, for a third SSB that may be associatedwith system information of the cell, where the third SSB may bescheduled for receipt in the second resource and performing radiofrequency retuning from the second resource to the operating bandwidthof the UE between monitoring for the third SSB and receiving the controlsignaling.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the controlsignaling may include operations, features, means, or instructions forreceiving the control signaling via a DCI message that includes one ormore fields that schedule the first SSB on the first resource.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the controlsignaling may include operations, features, means, or instructions forreceiving the control signaling via a DCI message that includes a fieldthat enables the monitoring for the first SSB, the DCI message alsoincluding scheduling information for one or more shared channeltransmissions.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving additionalcontrol signaling that schedules a frequency position of the first SSBwithin the radio frequency bandwidth, the additional control signalingreceived prior to the DCI message.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the controlsignaling may include operations, features, means, or instructions forreceiving the control signaling via a DCI message that includes anindication of one or more measurements associated with the first SSB.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the controlsignaling may include operations, features, means, or instructions forreceiving the control signaling via a group common DCI message.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the controlsignaling may include operations, features, means, or instructions forreceiving the control signaling via a MAC-CE that enables the monitoringfor the first SSB.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving secondcontrol signaling that schedules a set of semi-persistent SSBs in arespective set of resources within the operating bandwidth of the UE,the set of semi-persistent SSBs including the first SSB, and the MAC-CEenabling the monitoring for the set of semi-persistent SSBs.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving third controlsignaling deactivating the set of semi-persistent SSBs and monitoringfor a third SSB in a third resource outside of the operating bandwidthof the UE based on the third control signaling, where the second SSB andthe third SSB may be each part of a periodic set of SSBs in a respectiveset of resources outside of the operating bandwidth of the UE.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for performing one of aradio resource management procedure, a radio link monitoring procedure,or a bidirectional forwarding detection procedure based on themonitoring of the first SSB.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the second SSB includes acell-defining SSB and the first SSB includes a non-cell-defining SSB.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting, to anetwork entity, a first control message indicating that the UE may beentering a reduced capability mode and receiving, from the networkentity, a second control message configuring the operating bandwidth ofthe UE based on the first control message.

A method for wireless communications at a network entity is described.The method may include identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, transmitting, based onidentifying the operating bandwidth for communications with the UE,control signaling that schedules or enables a second SSB in a secondresource of the operating bandwidth of the UE, and transmitting thesecond SSB in the second resource.

An apparatus for wireless communications at a network entity isdescribed. The apparatus may include at least one processor, memorycoupled with the at least one processor, and instructions stored in thememory. The instructions may be executable by the at least one processorto cause the network entity to identify an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, transmit, based onidentifying the operating bandwidth for communications with the UE,control signaling that schedules or enables a second SSB in a secondresource of the operating bandwidth of the UE, and transmit the secondSSB in the second resource.

Another apparatus for wireless communications at a network entity isdescribed. The apparatus may include means for identifying an operatingbandwidth for communications with a UE, where a first SSB is scheduledfor transmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, means for transmitting,based on identifying the operating bandwidth for communications with theUE, control signaling that schedules or enables a second SSB in a secondresource of the operating bandwidth of the UE, and means fortransmitting the second SSB in the second resource.

A non-transitory computer-readable medium storing code for wirelesscommunications at a network entity is described. The code may includeinstructions executable by at least one processor to identify anoperating bandwidth for communications with a UE, where a first SSB isscheduled for transmission in a first resource that is outside of theoperating bandwidth of the UE, and where the first SSB is associatedwith system information of a cell that operates across a radio frequencybandwidth that includes the operating bandwidth of the UE, transmit,based on identifying the operating bandwidth for communications with theUE, control signaling that schedules or enables a second SSB in a secondresource of the operating bandwidth of the UE, and transmit the secondSSB in the second resource.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying that alatency target associated with a data transmission for the UE exceeds athreshold, where transmitting the control signaling may be based on theidentifying.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying that apayload size associated with a data transmission for the UE exceeds athreshold, where transmitting the control signaling may be based on theidentifying.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the controlsignaling may include operations, features, means, or instructions fortransmitting the control signaling via a DCI message that includes oneor more fields that schedule the second SSB on the second resource.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the controlsignaling may include operations, features, means, or instructions fortransmitting the control signaling via a DCI message that includes afield that enables monitoring at the UE for the second SSB, the DCImessage also including scheduling information for one or more sharedchannel transmissions.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting additionalcontrol signaling that schedules a frequency position of the second SSBwithin the radio frequency bandwidth, the additional control signalingreceived prior to the DCI message.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the controlsignaling may include operations, features, means, or instructions fortransmitting the control signaling via a DCI message that includes anindication of one or more measurements associated with the second SSB.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the controlsignaling may include operations, features, means, or instructions fortransmitting the control signaling via a group common DCI message.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the controlsignaling may include operations, features, means, or instructions fortransmitting the control signaling via a MAC-CE that enables monitoringat the UE for the second SSB.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting secondcontrol signaling that schedules a set of semi-persistent SSBs in arespective set of resources within the operating bandwidth of the UE,the set of semi-persistent SSBs including the second SSB, and the MAC-CEenabling monitoring at the UE for the set of semi-persistent SSBs.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting thirdcontrol signaling deactivating the set of semi-persistent SSBs andtransmitting a third SSB in a third resource outside of the operatingbandwidth of the UE based on the third control signaling, where thesecond SSB and the third SSB may be each part of a periodic set of SSBsin a respective set of resources outside of the operating bandwidth ofthe UE.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first SSB includes acell-defining SSB and the second SSB includes a non-cell-defining SSB.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving, from the UE,a first control message indicating that the UE may be entering a reducedcapability mode and transmitting, to the UE, a second control messageconfiguring the operating bandwidth of the UE based on the first controlmessage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system thatsupports configuring bandwidth parts (BWPs) and synchronization signalblocks (SSBs) in accordance with one or more aspects of the presentdisclosure.

FIG. 2 illustrates an example of a wireless communications system thatsupports configuring BWPs and SSBs in accordance with one or moreaspects of the present disclosure.

FIG. 3 illustrates an example of a resource diagram that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure.

FIG. 4 illustrates an example of a process flow that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure.

FIGS. 5 and 6 show block diagrams of devices that support configuringBWPs and SSBs in accordance with one or more aspects of the presentdisclosure.

FIG. 7 shows a block diagram of a communications manager that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure.

FIG. 8 shows a diagram of a system including a device that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure.

FIGS. 9 and 10 show block diagrams of devices that support configuringBWPs and SSBs in accordance with one or more aspects of the presentdisclosure.

FIG. 11 shows a block diagram of a communications manager that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure.

FIG. 12 shows a diagram of a system including a device that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure.

FIGS. 13 through 22 show flowcharts illustrating methods that supportconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure.

DETAILED DESCRIPTION

In some wireless communications systems, a user equipment (UE) ormultiple UEs may operate in a reduced capability mode or an enhancedreduced capability mode, for example, in order to save power. In areduced capability mode or an enhanced reduced capability mode, a UE mayoperate in a narrower bandwidth (e.g., a bandwidth part (BWP)) than theserving cell bandwidth. For example, a serving cell bandwidth may be 100MHz, a reduced capability bandwidth may be 20 MHz, and an enhancedreduced capability bandwidth may be 5 MHz. For example, use cases for anenhanced reduced capability mode may include metering devices, assettracking, and personal internet of things (IoT) devices. Reducedcapability modes and enhanced reduced capability modes may be associatedwith relaxed peak throughput, latency, and reliability targets.

UEs may monitor for and perform measurements on synchronization signalblocks (SSBs) transmitted by a network entity for purposes such as beammanagement, radio resource management, bidirectional forwardingdetection, and radio link monitoring. A network entity may transmit acell defining SSB (CD-SSB) periodically. The CD-SSB may be transmittedoutside of the operating bandwidth of a UE operating in a reducedcapability mode or an enhanced reduced capability mode. For example, theCD-SSB may be centered in the serving cell bandwidth, and the 20 MHzoperating bandwidth of a reduced capability UE or the 5 MHz operatingbandwidth of an enhanced reduced capability UE may be far away from thecenter of the serving cell bandwidth. For efficient user multiplexing orresource utilization for 5 MHz operating bandwidth enhanced reducedcapability mode UEs, more BWPs may be utilized in order to use at leastthe same amount of resources as 20 MHz operating bandwidth reducedcapability UEs.

In some examples, periodic non-cell defining SSBs (NCD-SSBs) may beconfigured via radio resource control (RRC) for each operating bandwidthfor each reduced capability UE or for each enhanced reduced capabilityUE. Configuring and transmitting periodic NCD-SSBs for each for eachreduced capability UE or enhanced reduced capability UE, however, mayincrease control resource overhead. For example, in a case where anetwork entity transmits one periodic NCD-SSB for a 100 MHz carrier,resource overhead associated with the NCD-SSB for the carrier may beapproximately 1%. If multiple reduced capability or enhanced reducedcapability UEs are operating at different operating bandwidths within acarrier bandwidth, and a different NCD-SSB is configured for eachoperating bandwidth, SSB overhead may significantly increase. Further,transmission of multiple NCD-SSBs may increase corresponding inter-cellinterference. For example, SSB overhead may increase by 7 times forenhanced reduced capability UEs. For example, for 8 NCD-SSB beams orbursts, in a time division duplexing scheme (downlink to uplink ratio of3), with a 100 MHz carrier bandwidth, and an NCD-SSB periodicity of 20ms, SSB overhead for the carrier bandwidth may be approximately 3-4%. Asanother example, for 4 NCD-SSB beams or bursts, in a frequency divisionduplexing scheme, with a 20 MHz carrier bandwidth, and an NCD-SSBperiodicity of 20 ms, SSB overhead for the carrier bandwidth may beapproximately 3-4%.

In some examples, a reduced capability UE or an enhanced reducedcapability UE may be configured via RRC to periodically switch back tothe frequency resource (e.g., the bandwidth in which the CD-SSB) istransmitted in order to monitor for the CD-SSB. For example, RRC maydefine a measurement gap inside of a carrier bandwidth but outside ofthe operating bandwidth of the reduced capability UE or an enhancedreduced capability UE. The measurement gap may include the SSB-basedradio resource management measurement timing configuration (SMTC) windowduration and a duration for radio frequency (RF) retuning. However,during the duration when the reduced capability UE or enhanced reducedcapability UE switches its RF circuitry outside of the operatingbandwidth to monitor for the CD-SSB, the reduced capability UE orenhanced reduced capability UE may be unable to communicate data usingthe configured operating bandwidth. As a result, throughput loss mayresult from a number of measurement gaps being configured for a UE.Accordingly, switching out of an operating bandwidth may negativelyimpact communications of large data payloads for the UE orcommunications with low latency targets.

Control signaling may dynamically configure an NCD-SSB. A reducedcapability UE or an enhanced reduced capability UE may receive adownlink control information (DCI) message or a medium access control(MAC) control element (CE) that schedules or enables an NCD-SSB that iswithin the UE's operating bandwidth. The UE may monitor for the NCD-SSBin the indicated resource and skip monitoring for the CD-SSB based onthe dynamic indication of the resource for the NCD-SSB. For example, areduced capability UE or an enhanced reduced capability UE may monitorfor the NCD-SSB without performing RF retuning between receiving thecontrol signaling and monitoring for the NCD-SSB. In some cases, thenetwork entity may schedule the NCD-SSB based on a latency target or apayload size of communications with the UE.

Aspects of the disclosure are initially described in the context ofwireless communications systems. Aspects of the disclosure are furtherillustrated by and described with reference to resource diagrams andprocess flows. Aspects of the disclosure are further illustrated by anddescribed with reference to apparatus diagrams, system diagrams, andflowcharts that relate to configuring BWPs and SSBs.

FIG. 1 illustrates an example of a wireless communications system 100that supports configuring BWPs and SSBs in accordance with one or moreaspects of the present disclosure. The wireless communications system100 may include one or more network entities 105, one or more UEs 115,and a core network 130. In some examples, the wireless communicationssystem 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced(LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or anetwork operating in accordance with other systems and radiotechnologies, including future systems and radio technologies notexplicitly mentioned herein.

The network entities 105 may be dispersed throughout a geographic areato form the wireless communications system 100 and may include devicesin different forms or having different capabilities. In variousexamples, a network entity 105 may be referred to as a network element,a mobility element, a radio access network (RAN) node, or networkequipment, among other nomenclature. In some examples, network entities105 and UEs 115 may wirelessly communicate via one or more communicationlinks 125 (e.g., a radio frequency (RF) access link). For example, anetwork entity 105 may support a coverage area 110 (e.g., a geographiccoverage area) over which the UEs 115 and the network entity 105 mayestablish one or more communication links 125. The coverage area 110 maybe an example of a geographic area over which a network entity 105 and aUE 115 may support the communication of signals according to one or moreradio access technologies (RATs).

The UEs 115 may be dispersed throughout a coverage area 110 of thewireless communications system 100, and each UE 115 may be stationary,or mobile, or both at different times. The UEs 115 may be devices indifferent forms or having different capabilities. Some example UEs 115are illustrated in FIG. 1 . The UEs 115 described herein may be able tocommunicate with various types of devices, such as other UEs 115 ornetwork entities 105, as shown in FIG. 1 .

As described herein, anode of the wireless communications system 100,which may be referred to as a network node, or a wireless node, may be anetwork entity 105 (e.g., any network entity described herein), a UE 115(e.g., any UE described herein), a network controller, an apparatus, adevice, a computing system, one or more components, or another suitableprocessing entity configured to perform any of the techniques describedherein. For example, a node may be a UE 115. As another example, a nodemay be a network entity 105. As another example, a first node may beconfigured to communicate with a second node or a third node. In oneaspect of this example, the first node may be a UE 115, the second nodemay be a network entity 105, and the third node may be a UE 115. Inanother aspect of this example, the first node may be a UE 115, thesecond node may be a network entity 105, and the third node may be anetwork entity 105. In yet other aspects of this example, the first,second, and third nodes may be different relative to these examples.Similarly, reference to a UE 115, network entity 105, apparatus, device,computing system, or the like may include disclosure of the UE 115,network entity 105, apparatus, device, computing system, or the likebeing a node. For example, disclosure that a UE 115 is configured toreceive information from a network entity 105 also discloses that afirst node is configured to receive information from a second node.

In some examples, network entities 105 may communicate with the corenetwork 130, or with one another, or both. For example, network entities105 may communicate with the core network 130 via one or more backhaulcommunication links 120 (e.g., in accordance with an S1, N2, N3, orother interface protocol). In some examples, network entities 105 maycommunicate with one another over a backhaul communication link 120(e.g., in accordance with an X2, Xn, or other interface protocol) eitherdirectly (e.g., directly between network entities 105) or indirectly(e.g., via a core network 130). In some examples, network entities 105may communicate with one another via a midhaul communication link 162(e.g., in accordance with a midhaul interface protocol) or a fronthaulcommunication link 168 (e.g., in accordance with a fronthaul interfaceprotocol), or any combination thereof. The backhaul communication links120, midhaul communication links 162, or fronthaul communication links168 may be or include one or more wired links (e.g., an electrical link,an optical fiber link), one or more wireless links (e.g., a radio link,a wireless optical link), among other examples or various combinationsthereof. A UE 115 may communicate with the core network 130 through acommunication link 155.

One or more of the network entities 105 described herein may include ormay be referred to as a base station 140 (e.g., a base transceiverstation, a radio base station, an NR base station, an access point, aradio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB ora giga-NodeB (either of which may be referred to as a gNB), a 5G NB, anext-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or othersuitable terminology). In some examples, a network entity 105 (e.g., abase station 140) may be implemented in an aggregated (e.g., monolithic,standalone) base station architecture, which may be configured toutilize a protocol stack that is physically or logically integratedwithin a single network entity 105 (e.g., a single RAN node, such as abase station 140).

In some examples, a network entity 105 may be implemented in adisaggregated architecture (e.g., a disaggregated base stationarchitecture, a disaggregated RAN architecture), which may be configuredto utilize a protocol stack that is physically or logically distributedamong two or more network entities 105, such as an integrated accessbackhaul (IAB) network, an open RAN (O-RAN) (e.g., a networkconfiguration sponsored by the O-RAN Alliance), or a virtualized RAN(vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105may include one or more of a central unit (CU) 160, a distributed unit(DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175(e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RTRIC)), a Service Management and Orchestration (SMO) 180 system, or anycombination thereof. An RU 170 may also be referred to as a radio head,a smart radio head, a remote radio head (RRH), a remote radio unit(RRU), or a transmission reception point (TRP). One or more componentsof the network entities 105 in a disaggregated RAN architecture may beco-located, or one or more components of the network entities 105 may belocated in distributed locations (e.g., separate physical locations). Insome examples, one or more network entities 105 of a disaggregated RANarchitecture may be implemented as virtual units (e.g., a virtual CU(VCU), a virtual DU (VDU), a virtual RU (VRU)).

The split of functionality between a CU 160, a DU 165, and an RU 170 isflexible and may support different functionalities depending upon whichfunctions (e.g., network layer functions, protocol layer functions,baseband functions, RF functions, and any combinations thereof) areperformed at a CU 160, a DU 165, or an RU 170. For example, a functionalsplit of a protocol stack may be employed between a CU 160 and a DU 165such that the CU 160 may support one or more layers of the protocolstack and the DU 165 may support one or more different layers of theprotocol stack. In some examples, the CU 160 may host upper protocollayer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling(e.g., Radio Resource Control (RRC), service data adaption protocol(SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may beconnected to one or more DUs 165 or RUs 170, and the one or more DUs 165or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g.,physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, MAClayer) functionality and signaling, and may each be at least partiallycontrolled by the CU 160. Additionally, or alternatively, a functionalsplit of the protocol stack may be employed between a DU 165 and an RU170 such that the DU 165 may support one or more layers of the protocolstack and the RU 170 may support one or more different layers of theprotocol stack. The DU 165 may support one or multiple different cells(e.g., via one or more RUs 170). In some cases, a functional splitbetween a CU 160 and a DU 165, or between a DU 165 and an RU 170 may bewithin a protocol layer (e.g., some functions for a protocol layer maybe performed by one of a CU 160, a DU 165, or an RU 170, while otherfunctions of the protocol layer are performed by a different one of theCU 160, the DU 165, or the RU 170). A CU 160 may be functionally splitfurther into CU control plane (CU-CP) and CU user plane (CU-UP)functions. A CU 160 may be connected to one or more DUs 165 via amidhaul communication link 162 (e.g., F1, F1-c, F1-u), and a DU 165 maybe connected to one or more RUs 170 via a fronthaul communication link168 (e.g., open fronthaul (FH) interface). In some examples, a midhaulcommunication link 162 or a fronthaul communication link 168 may beimplemented in accordance with an interface (e.g., a channel) betweenlayers of a protocol stack supported by respective network entities 105that are in communication over such communication links.

In wireless communications systems (e.g., wireless communications system100), infrastructure and spectral resources for radio access may supportwireless backhaul link capabilities to supplement wired backhaulconnections, providing an IAB network architecture (e.g., to a corenetwork 130). In some cases, in an IAB network, one or more networkentities 105 (e.g., IAB nodes 104) may be partially controlled by eachother. One or more IAB nodes 104 may be referred to as a donor entity oran IAB donor. One or more DUs 165 or one or more RUs 170 may bepartially controlled by one or more CUs 160 associated with a donornetwork entity 105 (e.g., a donor base station 140). The one or moredonor network entities 105 (e.g., IAB donors) may be in communicationwith one or more additional network entities 105 (e.g., IAB nodes 104)via supported access and backhaul links (e.g., backhaul communicationlinks 120). IAB nodes 104 may include an IAB mobile termination (IAB-MT)controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. AnIAB-MT may include an independent set of antennas for relay ofcommunications with UEs 115, or may share the same antennas (e.g., of anRU 170) of an IAB node 104 used for access via the DU 165 of the IABnode 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In someexamples, the IAB nodes 104 may include DUs 165 that supportcommunication links with additional entities (e.g., IAB nodes 104, UEs115) within the relay chain or configuration of the access network(e.g., downstream). In such cases, one or more components of thedisaggregated RAN architecture (e.g., one or more IAB nodes 104 orcomponents of IAB nodes 104) may be configured to operate according tothe techniques described herein.

For instance, an access network (AN) or RAN may include communicationsbetween access nodes (e.g., an IAB donor), IAB nodes 104, and one ormore UEs 115. The IAB donor may facilitate connection between the corenetwork 130 and the AN (e.g., via a wired or wireless connection to thecore network 130). That is, an IAB donor may refer to a RAN node with awired or wireless connection to core network 130. The IAB donor mayinclude a CU 160 and at least one DU 165 (e.g., and RU 170), in whichcase the CU 160 may communicate with the core network 130 over aninterface (e.g., a backhaul link). IAB donor and IAB nodes 104 maycommunicate over an F1 interface according to a protocol that definessignaling messages (e.g., an F1 AP protocol). Additionally, oralternatively, the CU 160 may communicate with the core network over aninterface, which may be an example of a portion of backhaul link, andmay communicate with other CUs 160 (e.g., a CU 160 associated with analternative IAB donor) over an Xn-C interface, which may be an exampleof a portion of a backhaul link.

An IAB node 104 may refer to a RAN node that provides IAB functionality(e.g., access for UEs 115, wireless self-backhauling capabilities). A DU165 may act as a distributed scheduling node towards child nodesassociated with the IAB node 104, and the IAB-MT may act as a schedulednode towards parent nodes associated with the IAB node 104. That is, anIAB donor may be referred to as a parent node in communication with oneor more child nodes (e.g., an IAB donor may relay transmissions for UEsthrough one or more other IAB nodes 104). Additionally, oralternatively, an IAB node 104 may also be referred to as a parent nodeor a child node to other IAB nodes 104, depending on the relay chain orconfiguration of the AN. Therefore, the IAB-MT entity of IAB nodes 104may provide a Uu interface for a child IAB node 104 to receive signalingfrom a parent IAB node 104, and the DU interface (e.g., DUs 165) mayprovide a Uu interface for a parent IAB node 104 to signal to a childIAB node 104 or UE 115.

For example, IAB node 104 may be referred to as a parent node thatsupports communications for a child IAB node, and referred to as a childIAB node associated with an IAB donor. The IAB donor may include a CU160 with a wired or wireless connection (e.g., a backhaul communicationlink 120) to the core network 130 and may act as parent node to IABnodes 104. For example, the DU 165 of IAB donor may relay transmissionsto UEs 115 through IAB nodes 104, and may directly signal transmissionsto a UE 115. The CU 160 of IAB donor may signal communication linkestablishment via an F1 interface to IAB nodes 104, and the IAB nodes104 may schedule transmissions (e.g., transmissions to the UEs 115relayed from the IAB donor) through the DUs 165. That is, data may berelayed to and from IAB nodes 104 via signaling over an NR Uu interfaceto MT of the IAB node 104. Communications with IAB node 104 may bescheduled by a DU 165 of IAB donor and communications with IAB node 104may be scheduled by DU 165 of IAB node 104.

In the case of the techniques described herein applied in the context ofa disaggregated RAN architecture, one or more components of thedisaggregated RAN architecture may be configured to support configuringBWPs and SSBs as described herein. For example, some operationsdescribed as being performed by a UE 115 or a network entity 105 (e.g.,a base station 140) may additionally, or alternatively, be performed byone or more components of the disaggregated RAN architecture (e.g., IABnodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).

A UE 115 may include or may be referred to as a mobile device, awireless device, a remote device, a handheld device, or a subscriberdevice, or some other suitable terminology, where the “device” may alsobe referred to as a unit, a station, a terminal, or a client, amongother examples. A UE 115 may also include or may be referred to as apersonal electronic device such as a cellular phone, a personal digitalassistant (PDA), a multimedia/entertainment device (e.g., a radio, a MP3player, or a video device, etc.), a camera, a gaming device, anavigation/positioning device (e.g., GNSS (global navigation satellitesystem) devices based on, for example, GPS (global positioning system),Beidou, GLONASS, or Galileo, or a terrestrial-based device, a tabletcomputer, a laptop computer, a netbook, a smartbook, a personalcomputer, a smart device, a wearable device (e.g., a smart watch, smartclothing, smart glasses, virtual reality goggles, a smart wristband,smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, arobot/robotic device, a vehicle, a vehicular device, a meter (e.g.,parking meter, electric meter, gas meter, water meter), a monitor, a gaspump, an appliance (e.g., kitchen appliance, washing machine, dryer), alocation tag, a medical/healthcare device, an implant, asensor/actuator, a display, or any other suitable device configured tocommunicate via a wireless or wired medium. In some examples, a UE 115may include or be referred to as a wireless local loop (WLL) station, anIoT device, an Internet of Everything (IoE) device, or a machine typecommunications (MTC) device, among other examples, which may beimplemented in various objects such as appliances, or vehicles, meters,among other examples.

The UEs 115 described herein may be able to communicate with varioustypes of devices, such as other UEs 115 that may sometimes act as relaysas well as the network entities 105 and the network equipment includingmacro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations,among other examples, as shown in FIG. 1 .

The UEs 115 and the network entities 105 may wirelessly communicate withone another via one or more communication links 125 (e.g., an accesslink) over one or more carriers. The term “carrier” may refer to a setof RF spectrum resources having a defined physical layer structure forsupporting the communication links 125. For example, a carrier used fora communication link 125 may include a portion of a RF spectrum band(e.g., a BWP) that is operated according to one or more physical layerchannels for a given radio access technology (e.g., LTE, LTE-A, LTE-APro, NR). Each physical layer channel may carry acquisition signaling(e.g., synchronization signals, system information), control signalingthat coordinates operation for the carrier, user data, or othersignaling. The wireless communications system 100 may supportcommunication with a UE 115 using carrier aggregation or multi-carrieroperation. A UE 115 may be configured with multiple downlink componentcarriers and one or more uplink component carriers according to acarrier aggregation configuration. Carrier aggregation may be used withboth frequency division duplexing (FDD) and time division duplexing(TDD) component carriers. Communication between a network entity 105 andother devices may refer to communication between the devices and anyportion (e.g., entity, sub-entity) of a network entity 105. For example,the terms “transmitting,” “receiving,” or “communicating,” whenreferring to a network entity 105, may refer to any portion of a networkentity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of aRAN communicating with another device (e.g., directly or via one or moreother network entities 105).

In some examples, such as in a carrier aggregation configuration, acarrier may also have acquisition signaling or control signaling thatcoordinates operations for other carriers. A carrier may be associatedwith a frequency channel (e.g., an evolved universal mobiletelecommunication system terrestrial radio access (E-UTRA) absolute RFchannel number (EARFCN)) and may be positioned according to a channelraster for discovery by the UEs 115. A carrier may be operated in astandalone mode, in which case initial acquisition and connection may beconducted by the UEs 115 via the carrier, or the carrier may be operatedin a non-standalone mode, in which case a connection is anchored using adifferent carrier (e.g., of the same or a different radio accesstechnology).

The communication links 125 shown in the wireless communications system100 may include downlink transmissions (e.g., forward linktransmissions) from a network entity 105 to a UE 115, uplinktransmissions (e.g., return link transmissions) from a UE 115 to anetwork entity 105, or both, among other configurations oftransmissions. Carriers may carry downlink or uplink communications(e.g., in an FDD mode) or may be configured to carry downlink and uplinkcommunications (e.g., in a TDD mode).

A carrier may be associated with a particular bandwidth of the RFspectrum and, in some examples, the carrier bandwidth may be referred toas a “system bandwidth” of the carrier or the wireless communicationssystem 100. For example, the carrier bandwidth may be one of a set ofbandwidths for carriers of a particular radio access technology (e.g.,1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of thewireless communications system 100 (e.g., the network entities 105, theUEs 115, or both) may have hardware configurations that supportcommunications over a particular carrier bandwidth or may beconfigurable to support communications over one of a set of carrierbandwidths. In some examples, the wireless communications system 100 mayinclude network entities 105 or UEs 115 that support concurrentcommunications via carriers associated with multiple carrier bandwidths.In some examples, each served UE 115 may be configured for operatingover portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiplesubcarriers (e.g., using multi-carrier modulation (MCM) techniques suchas orthogonal frequency division multiplexing (OFDM) or discrete Fouriertransform spread OFDM (DFT-S-OFDM)). In a system employing MCMtechniques, a resource element may refer to resources of one symbolperiod (e.g., a duration of one modulation symbol) and one subcarrier,in which case the symbol period and subcarrier spacing may be inverselyrelated. The quantity of bits carried by each resource element maydepend on the modulation scheme (e.g., the order of the modulationscheme, the coding rate of the modulation scheme, or both) such that themore resource elements that a device receives and the higher the orderof the modulation scheme, the higher the data rate may be for thedevice. A wireless communications resource may refer to a combination ofan RF spectrum resource, a time resource, and a spatial resource (e.g.,a spatial layer, a beam), and the use of multiple spatial resources mayincrease the data rate or data integrity for communications with a UE115.

One or more numerologies for a carrier may be supported, where anumerology may include a subcarrier spacing (Δf) and a cyclic prefix. Acarrier may be divided into one or more BWPs having the same ordifferent numerologies. In some examples, a UE 115 may be configuredwith multiple BWPs. In some examples, a single BWP for a carrier may beactive at a given time and communications for the UE 115 may berestricted to one or more active BWPs.

The time intervals for the network entities 105 or the UEs 115 may beexpressed in multiples of a basic time unit which may, for example,refer to a sampling period of T_(s)=1/(Δf_(max)·N_(f)) seconds, whereΔf_(max) may represent the maximum supported subcarrier spacing, andN_(f) may represent the maximum supported discrete Fourier transform(DFT) size. Time intervals of a communications resource may be organizedaccording to radio frames each having a specified duration (e.g., 10milliseconds (ms)). Each radio frame may be identified by a system framenumber (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes orslots, and each subframe or slot may have the same duration. In someexamples, a frame may be divided (e.g., in the time domain) intosubframes, and each subframe may be further divided into a quantity ofslots. Alternatively, each frame may include a variable quantity ofslots, and the quantity of slots may depend on subcarrier spacing. Eachslot may include a quantity of symbol periods (e.g., depending on thelength of the cyclic prefix prepended to each symbol period). In somewireless communications systems 100, a slot may further be divided intomultiple mini-slots containing one or more symbols. Excluding the cyclicprefix, each symbol period may contain one or more (e.g., N_(f))sampling periods. The duration of a symbol period may depend on thesubcarrier spacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallestscheduling unit (e.g., in the time domain) of the wirelesscommunications system 100 and may be referred to as a transmission timeinterval (TTI). In some examples, the TTI duration (e.g., a quantity ofsymbol periods in a TTI) may be variable. Additionally, oralternatively, the smallest scheduling unit of the wirelesscommunications system 100 may be dynamically selected (e.g., in burstsof shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to varioustechniques. A physical control channel and a physical data channel maybe multiplexed on a downlink carrier, for example, using one or more oftime division multiplexing (TDM) techniques, frequency divisionmultiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A controlregion (e.g., a control resource set (CORESET)) for a physical controlchannel may be defined by a set of symbol periods and may extend acrossthe system bandwidth or a subset of the system bandwidth of the carrier.One or more control regions (e.g., CORESETs) may be configured for a setof the UEs 115. For example, one or more of the UEs 115 may monitor orsearch control regions for control information according to one or moresearch space sets, and each search space set may include one or multiplecontrol channel candidates in one or more aggregation levels arranged ina cascaded manner. An aggregation level for a control channel candidatemay refer to an amount of control channel resources (e.g., controlchannel elements (CCEs)) associated with encoded information for acontrol information format having a given payload size. Search spacesets may include common search space sets configured for sending controlinformation to multiple UEs 115 and UE-specific search space sets forsending control information to a specific UE 115.

A network entity 105 may provide communication coverage via one or morecells, for example a macro cell, a small cell, a hot spot, or othertypes of cells, or any combination thereof. The term “cell” may refer toa logical communication entity used for communication with a networkentity 105 (e.g., over a carrier) and may be associated with anidentifier for distinguishing neighboring cells (e.g., a physical cellidentifier (PCID), a virtual cell identifier (VCID), or others). In someexamples, a cell may also refer to a coverage area 110 or a portion of acoverage area 110 (e.g., a sector) over which the logical communicationentity operates. Such cells may range from smaller areas (e.g., astructure, a subset of structure) to larger areas depending on variousfactors such as the capabilities of the network entity 105. For example,a cell may be or include a building, a subset of a building, or exteriorspaces between or overlapping with coverage areas 110, among otherexamples.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by theUEs 115 with service subscriptions with the network provider supportingthe macro cell. A small cell may be associated with a lower-powerednetwork entity 105 (e.g., a lower-powered base station 140), as comparedwith a macro cell, and a small cell may operate in the same or different(e.g., licensed, unlicensed) frequency bands as macro cells. Small cellsmay provide unrestricted access to the UEs 115 with servicesubscriptions with the network provider or may provide restricted accessto the UEs 115 having an association with the small cell (e.g., the UEs115 in a closed subscriber group (CSG), the UEs 115 associated withusers in a home or office). A network entity 105 may support one ormultiple cells and may also support communications over the one or morecells using one or multiple component carriers.

In some examples, a carrier may support multiple cells, and differentcells may be configured according to different protocol types (e.g.,MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that mayprovide access for different types of devices.

In some examples, a network entity 105 (e.g., a base station 140, an RU170) may be movable and therefore provide communication coverage for amoving coverage area 110. In some examples, different coverage areas 110associated with different technologies may overlap, but the differentcoverage areas 110 may be supported by the same network entity 105. Insome other examples, the overlapping coverage areas 110 associated withdifferent technologies may be supported by different network entities105. The wireless communications system 100 may include, for example, aheterogeneous network in which different types of the network entities105 provide coverage for various coverage areas 110 using the same ordifferent radio access technologies.

The wireless communications system 100 may support synchronous orasynchronous operation. For synchronous operation, network entities 105(e.g., base stations 140) may have similar frame timings, andtransmissions from different network entities 105 may be approximatelyaligned in time. For asynchronous operation, network entities 105 mayhave different frame timings, and transmissions from different networkentities 105 may, in some examples, not be aligned in time. Thetechniques described herein may be used for either synchronous orasynchronous operations.

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices and may provide for automated communication betweenmachines (e.g., via Machine-to-Machine (M2M) communication). M2Mcommunication or MTC may refer to data communication technologies thatallow devices to communicate with one another or a network entity 105(e.g., a base station 140) without human intervention. In some examples,M2M communication or MTC may include communications from devices thatintegrate sensors or meters to measure or capture information and relaysuch information to a central server or application program that makesuse of the information or presents the information to humans interactingwith the application program. Some UEs 115 may be designed to collectinformation or enable automated behavior of machines or other devices.Examples of applications for MTC devices include smart metering,inventory monitoring, water level monitoring, equipment monitoring,healthcare monitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging. In anaspect, techniques disclosed herein may be applicable to MTC or IoT UEs.MTC or IoT UEs may include MTC/enhanced MTC (eMTC, also referred to asCAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well asother types of UEs. eMTC and NB-IoT may refer to future technologiesthat may evolve from or may be based on these technologies. For example,eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC),and mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhancedNB-IoT), and FeNB-IoT (further enhanced NB-IoT).

Some UEs 115 may be configured to employ operating modes that reducepower consumption, such as half-duplex communications (e.g., a mode thatsupports one-way communication via transmission or reception, but nottransmission and reception concurrently). In some examples, half-duplexcommunications may be performed at a reduced peak rate. Other powerconservation techniques for the UEs 115 include entering a power savingdeep sleep mode when not engaging in active communications, operatingover a limited bandwidth (e.g., according to narrowband communications),or a combination of these techniques. For example, some UEs 115 may beconfigured for operation using a narrowband protocol type that isassociated with a defined portion or range (e.g., set of subcarriers orresource blocks (RBs)) within a carrier, within a guard-band of acarrier, or outside of a carrier.

The wireless communications system 100 may be configured to supportultra-reliable communications or low-latency communications, or variouscombinations thereof. For example, the wireless communications system100 may be configured to support ultra-reliable low-latencycommunications (URLLC). The UEs 115 may be designed to supportultra-reliable, low-latency, or critical functions. Ultra-reliablecommunications may include private communication or group communicationand may be supported by one or more services such as push-to-talk,video, or data. Support for ultra-reliable, low-latency functions mayinclude prioritization of services, and such services may be used forpublic safety or general commercial applications. The termsultra-reliable, low-latency, and ultra-reliable low-latency may be usedinterchangeably herein.

In some examples, a UE 115 may be able to communicate directly withother UEs 115 over a device-to-device (D2D) communication link 135(e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelinkprotocol). In some examples, one or more UEs 115 of a group that areperforming D2D communications may be within the coverage area 110 of anetwork entity 105 (e.g., a base station 140, an RU 170), which maysupport aspects of such D2D communications being configured by orscheduled by the network entity 105. In some examples, one or more UEs115 in such a group may be outside the coverage area 110 of a networkentity 105 or may be otherwise unable to or not configured to receivetransmissions from a network entity 105. In some examples, groups of theUEs 115 communicating via D2D communications may support a one-to-many(1:M) system in which each UE 115 transmits to each of the other UEs 115in the group. In some examples, a network entity 105 may facilitate thescheduling of resources for D2D communications. In some other examples,D2D communications may be carried out between the UEs 115 without theinvolvement of a network entity 105.

In some systems, a D2D communication link 135 may be an example of acommunication channel, such as a sidelink communication channel, betweenvehicles (e.g., UEs 115). In some examples, vehicles may communicateusing vehicle-to-everything (V2X) communications, vehicle-to-vehicle(V2V) communications, or some combination of these. A vehicle may signalinformation related to traffic conditions, signal scheduling, weather,safety, emergencies, or any other information relevant to a V2X system.In some examples, vehicles in a V2X system may communicate with roadsideinfrastructure, such as roadside units, or with the network via one ormore network nodes (e.g., network entities 105, base stations 140, RUs170) using vehicle-to-network (V2N) communications, or with both.

The core network 130 may provide user authentication, accessauthorization, tracking, Internet Protocol (IP) connectivity, and otheraccess, routing, or mobility functions. The core network 130 may be anevolved packet core (EPC) or 5G core (5GC), which may include at leastone control plane entity that manages access and mobility (e.g., amobility management entity (MME), an access and mobility managementfunction (AMF)) and at least one user plane entity that routes packetsor interconnects to external networks (e.g., a serving gateway (S-GW), aPacket Data Network (PDN) gateway (P-GW), or a user plane function(UPF)). The control plane entity may manage non-access stratum (NAS)functions such as mobility, authentication, and bearer management forthe UEs 115 served by the network entities 105 (e.g., base stations 140)associated with the core network 130. User IP packets may be transferredthrough the user plane entity, which may provide IP address allocationas well as other functions. The user plane entity may be connected to IPservices 150 for one or more network operators. The IP services 150 mayinclude access to the Internet, Intranet(s), an IP Multimedia Subsystem(IMS), or a Packet-Switched Streaming Service.

The wireless communications system 100 may operate using one or morefrequency bands, which may be in the range of 300 megahertz (MHz) to 300gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known asthe ultra-high frequency (UHF) region or decimeter band because thewavelengths range from approximately one decimeter to one meter inlength. The UHF waves may be blocked or redirected by buildings andenvironmental features, which may be referred to as clusters, but thewaves may penetrate structures sufficiently for a macro cell to provideservice to the UEs 115 located indoors. The transmission of UHF wavesmay be associated with smaller antennas and shorter ranges (e.g., lessthan 100 kilometers) compared to transmission using the smallerfrequencies and longer waves of the high frequency (HF) or very highfrequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may also operate in a super highfrequency (SHF) region using frequency bands from 3 GHz to 30 GHz, alsoknown as the centimeter band, or in an extremely high frequency (EHF)region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as themillimeter band. In some examples, the wireless communications system100 may support millimeter wave (mmW) communications between the UEs 115and the network entities 105 (e.g., base stations 140, RUs 170), and EHFantennas of the respective devices may be smaller and more closelyspaced than UHF antennas. In some examples, this may facilitate use ofantenna arrays within a device. The propagation of EHF transmissions,however, may be subject to even greater atmospheric attenuation andshorter range than SHF or UHF transmissions. The techniques disclosedherein may be employed across transmissions that use one or moredifferent frequency regions, and designated use of bands across thesefrequency regions may differ by country or regulating body.

The wireless communications system 100 may utilize both licensed andunlicensed RF spectrum bands. For example, the wireless communicationssystem 100 may employ License Assisted Access (LAA), LTE-Unlicensed(LTE-U) radio access technology, or NR technology in an unlicensed bandsuch as the 5 GHz industrial, scientific, and medical (ISM) band. Whileoperating in unlicensed RF spectrum bands, devices such as the networkentities 105 and the UEs 115 may employ carrier sensing for collisiondetection and avoidance. In some examples, operations in unlicensedbands may be based on a carrier aggregation configuration in conjunctionwith component carriers operating in a licensed band (e.g., LAA).Operations in unlicensed spectrum may include downlink transmissions,uplink transmissions, P2P transmissions, or D2D transmissions, amongother examples.

A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115may be equipped with multiple antennas, which may be used to employtechniques such as transmit diversity, receive diversity, multiple-inputmultiple-output (MIMO) communications, or beamforming. The antennas of anetwork entity 105 or a UE 115 may be located within one or more antennaarrays or antenna panels, which may support MIMO operations or transmitor receive beamforming. For example, one or more base station antennasor antenna arrays may be co-located at an antenna assembly, such as anantenna tower. In some examples, antennas or antenna arrays associatedwith a network entity 105 may be located in diverse geographiclocations. A network entity 105 may have an antenna array with a set ofrows and columns of antenna ports that the network entity 105 may use tosupport beamforming of communications with a UE 115. Likewise, a UE 115may have one or more antenna arrays that may support various MIMO orbeamforming operations. Additionally, or alternatively, an antenna panelmay support RF beamforming for a signal transmitted via an antenna port.

The network entities 105 or the UEs 115 may use MIMO communications toexploit multipath signal propagation and increase the spectralefficiency by transmitting or receiving multiple signals via differentspatial layers. Such techniques may be referred to as spatialmultiplexing. The multiple signals may, for example, be transmitted bythe transmitting device via different antennas or different combinationsof antennas. Likewise, the multiple signals may be received by thereceiving device via different antennas or different combinations ofantennas. Each of the multiple signals may be referred to as a separatespatial stream and may carry information associated with the same datastream (e.g., the same codeword) or different data streams (e.g.,different codewords). Different spatial layers may be associated withdifferent antenna ports used for channel measurement and reporting. MIMOtechniques include single-user MIMO (SU-MIMO), where multiple spatiallayers are transmitted to the same receiving device, and multiple-userMIMO (MU-MIMO), where multiple spatial layers are transmitted tomultiple devices.

Beamforming, which may also be referred to as spatial filtering,directional transmission, or directional reception, is a signalprocessing technique that may be used at a transmitting device or areceiving device (e.g., a network entity 105, a UE 115) to shape orsteer an antenna beam (e.g., a transmit beam, a receive beam) along aspatial path between the transmitting device and the receiving device.Beamforming may be achieved by combining the signals communicated viaantenna elements of an antenna array such that some signals propagatingat particular orientations with respect to an antenna array experienceconstructive interference while others experience destructiveinterference. The adjustment of signals communicated via the antennaelements may include a transmitting device or a receiving deviceapplying amplitude offsets, phase offsets, or both to signals carriedvia the antenna elements associated with the device. The adjustmentsassociated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device orreceiving device, or with respect to some other orientation).

A network entity 105 or a UE 115 may use beam sweeping techniques aspart of beamforming operations. For example, a network entity 105 (e.g.,a base station 140, an RU 170) may use multiple antennas or antennaarrays (e.g., antenna panels) to conduct beamforming operations fordirectional communications with a UE 115. Some signals (e.g.,synchronization signals, reference signals, beam selection signals, orother control signals) may be transmitted by a network entity 105multiple times along different directions. For example, the networkentity 105 may transmit a signal according to different beamformingweight sets associated with different directions of transmission.Transmissions along different beam directions may be used to identify(e.g., by a transmitting device, such as a network entity 105, or by areceiving device, such as a UE 115) a beam direction for latertransmission or reception by the network entity 105.

Some signals, such as data signals associated with a particularreceiving device, may be transmitted by transmitting device (e.g., atransmitting network entity 105, a transmitting UE 115) along a singlebeam direction (e.g., a direction associated with the receiving device,such as a receiving network entity 105 or a receiving UE 115). In someexamples, the beam direction associated with transmissions along asingle beam direction may be determined based on a signal that wastransmitted along one or more beam directions. For example, a UE 115 mayreceive one or more of the signals transmitted by the network entity 105along different directions and may report to the network entity 105 anindication of the signal that the UE 115 received with a highest signalquality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (e.g., by a network entity105 or a UE 115) may be performed using multiple beam directions, andthe device may use a combination of digital precoding or beamforming togenerate a combined beam for transmission (e.g., from a network entity105 to a UE 115). The UE 115 may report feedback that indicatesprecoding weights for one or more beam directions, and the feedback maycorrespond to a configured set of beams across a system bandwidth or oneor more sub-bands. The network entity 105 may transmit a referencesignal (e.g., a cell-specific reference signal (CRS), a channel stateinformation reference signal (CSI-RS)), which may be precoded orunprecoded. The UE 115 may provide feedback for beam selection, whichmay be a precoding matrix indicator (PMI) or codebook-based feedback(e.g., a multi-panel type codebook, a linear combination type codebook,a port selection type codebook). Although these techniques are describedwith reference to signals transmitted along one or more directions by anetwork entity 105 (e.g., a base station 140, an RU 170), a UE 115 mayemploy similar techniques for transmitting signals multiple times alongdifferent directions (e.g., for identifying a beam direction forsubsequent transmission or reception by the UE 115) or for transmittinga signal along a single direction (e.g., for transmitting data to areceiving device).

A receiving device (e.g., a UE 115) may perform reception operations inaccordance with multiple receive configurations (e.g., directionallistening) when receiving various signals from a receiving device (e.g.,a network entity 105), such as synchronization signals, referencesignals, beam selection signals, or other control signals. For example,a receiving device may perform reception in accordance with multiplereceive directions by receiving via different antenna subarrays, byprocessing received signals according to different antenna subarrays, byreceiving according to different receive beamforming weight sets (e.g.,different directional listening weight sets) applied to signals receivedat multiple antenna elements of an antenna array, or by processingreceived signals according to different receive beamforming weight setsapplied to signals received at multiple antenna elements of an antennaarray, any of which may be referred to as “listening” according todifferent receive configurations or receive directions. In someexamples, a receiving device may use a single receive configuration toreceive along a single beam direction (e.g., when receiving a datasignal). The single receive configuration may be aligned along a beamdirection determined based on listening according to different receiveconfiguration directions (e.g., a beam direction determined to have ahighest signal strength, highest signal-to-noise ratio (SNR), orotherwise acceptable signal quality based on listening according tomultiple beam directions).

The wireless communications system 100 may be a packet-based networkthat operates according to a layered protocol stack. In the user plane,communications at the bearer or PDCP layer may be IP-based. An RLC layermay perform packet segmentation and reassembly to communicate overlogical channels. A MAC layer may perform priority handling andmultiplexing of logical channels into transport channels. The MAC layermay also use error detection techniques, error correction techniques, orboth to support retransmissions at the MAC layer to improve linkefficiency. In the control plane, the RRC protocol layer may provideestablishment, configuration, and maintenance of an RRC connectionbetween a UE 115 and a network entity 105 or a core network 130supporting radio bearers for user plane data. At the PHY layer,transport channels may be mapped to physical channels.

The UEs 115 and the network entities 105 may support retransmissions ofdata to increase the likelihood that data is received successfully.Hybrid automatic repeat request (HARQ) feedback is one technique forincreasing the likelihood that data is received correctly over acommunication link (e.g., a communication link 125, a D2D communicationlink 135). HARQ may include a combination of error detection (e.g.,using a cyclic redundancy check (CRC)), forward error correction (FEC),and retransmission (e.g., automatic repeat request (ARQ)). HARQ mayimprove throughput at the MAC layer in poor radio conditions (e.g., lowsignal-to-noise conditions). In some examples, a device may supportsame-slot HARQ feedback, where the device may provide HARQ feedback in aspecific slot for data received in a previous symbol in the slot. Insome other examples, the device may provide HARQ feedback in asubsequent slot, or according to some other time interval.

A network entity 105 may dynamically schedule an SSB within an operatingbandwidth of a UE 115, where the operating bandwidth of the UE 115 isoutside of a frequency resource in which a CD-SSB is scheduled forreception. For example, a UE 115 may operate in a reduced capabilitymode or an enhanced reduced capability mode in order to save power. In areduced capability mode or an enhanced reduced capability mode, a UE 115may operate in a narrower bandwidth (e.g., a BWP) than the serving cellbandwidth. A network entity 105 may transmit control signaling that maydynamically schedule or enable an SSB for the UE 115 within theoperating bandwidth of the UE 115. A reduced capability UE 115 or anenhanced reduced capability UE 115 may receive a DCI message or a MAC-CEthat schedules or enables an NCD-SSB that is within the UE 115'soperating bandwidth. The UE 115 may monitor for the NCD-SSB in theindicated resource and skip monitoring for the CD-SSB based on thedynamic indication of the resource for the NCD-SSB. For example, areduced capability UE 115 or an enhanced reduced capability UE 115 maymonitor for the NCD-SSB without performing RF retuning between receivingthe control signaling and monitoring for the NCD-SSB. In some cases, thenetwork entity 105 may schedule the NCD-SSB based on a latency target ora payload size of communications with the UE 115.

FIG. 2 illustrates an example of a wireless communications system 200that supports configuring BWPs and SSBs in accordance with one or moreaspects of the present disclosure. In some examples, the wirelesscommunications system 200 may implement aspects of wirelesscommunications system 100. The wireless communications system 200 mayinclude a UE 115-a, which may be an example of a UE 115 as describedherein. The wireless communications system 200 may include a networkentity 105-a, which may be an example of a network entity 105 asdescribed herein.

The UE 115-a may communicate with the network entity 105-a using acommunication link 125-a, which may be examples of NR or LTE linksbetween the UE 115-a and the network entity 105-a. The communicationlink 125-a may include a bi-directional link that enables both uplinkand downlink communication. For example, the UE 115-a may transmituplink signals, such as uplink control signals or uplink data signals,to the network entity 105-a using the communication link 125-a and thenetwork entity 105-a may transmit downlink transmissions, such asdownlink control signals or downlink data signals, to the UE 115-a usingthe communication link 125-a.

The network entity 105-a may dynamically schedule an NCD-SSB 225 withinan operating bandwidth of a UE 115-a, where the operating bandwidth ofthe UE 115-a is outside of a first frequency resource in which a CD-SSB210 is scheduled for reception. The network entity 105-a may identify anoperating bandwidth for communications with the UE 115-a. A CD-SSB 210may be scheduled for transmission in a first resource that is outside ofthe operating bandwidth of the UE 115-a. The CD-SSB 210 may beassociated with system information of a cell that operates across aradio frequency bandwidth that includes the operating bandwidth of theUE 115-a.

In some cases, the network entity 105-a may receive, from the UE 115-a,a first control message 205 indicating that the UE 115-a is entering areduced capability mode or an enhanced reduced capability mode. Inresponse to the first control message 205, the network entity 105-a maytransmit, to the UE 115-a a second control message 215 configuring theoperating bandwidth of the UE 115-a. Accordingly, the network entity105-a may identify and configure an operating bandwidth of the UE 115-abased on receiving an indication that the UE 115-a is entering a reducedcapability mode or an enhanced reduced capability mode.

The network entity 105-a may transmit, to the UE 115-a, based onidentifying the operating bandwidth for communication with the UE 115-a,control signaling 220 that schedules or enables an NCD-SSB 225 in asecond resource of the operating bandwidth of the UE 115-a. The UE 115-amay monitor for, and the network entity 105-a may transmit, the NCD-SSB225 in the second resource.

In some cases, the network entity 105-a may identify that a latencytarget associated with a data transmission for the UE 115-a exceeds athreshold, and the network entity 105-a may transmit the controlsignaling 220 based on identifying that the latency target associatedwith the data transmission for the UE 115-a exceeds the threshold.

In some cases, the network entity 105-a may identify that a payload sizeof a data transmission for the UE 115-a exceeds a threshold, and thenetwork entity 105-a may transmit the control signaling 220 based onidentifying that the payload size of the data transmission for the UE115-a exceeds the threshold.

In some cases, transmitting the control signaling 220 includestransmitting the control signaling 220 via a DCI message that includesone or more fields that schedule the NCD-SSB 225 on the second resource.

In some cases, transmitting the control signaling 220 includestransmitting the control signaling 220 via a DCI message that includes afield that enables monitoring at the UE 115-a for the NCD-SSB 225. TheDCI message may also include scheduling information for one or moreshared channel transmissions. In some cases, the network entity 105-amay further transmit additional control signaling 230 that schedules afrequency position of the NCD-SSB 225 within the radio frequencybandwidth, the additional control signaling received prior to the DCImessage.

In some cases, transmitting the control signaling 220 includestransmitting the control signaling 22—via a DCI message that includes anindication of one or more measurements associated with the NCD-SSB 225.

In some cases, transmitting the control signaling 220 includestransmitting the control signaling 220 via a group common DCI message.For example, the network entity 105-a may communicate with a number ofUEs 115 including the UE 115-a, and the network entity 105-a maytransmit the control signaling 220 via a group common DCI message.

In some cases, transmitting the control signaling 220 includestransmitting the control signaling 220 via a MAC-CE that enablesmonitoring at the UE 115-a for the NCD-SSB 225. In some cases, thenetwork entity 105-a may further transmit second control signaling 235that schedules a set of semi-persistent SSBs in a respective set ofresources within the operating bandwidth of the UE 115-a, the set ofsemi-persistent SSBs including the NCD-SSB 225, and the MAC-CE enablingmonitoring at the UE 115-a for the set of semi-persistent SSBs. In somecases, the network entity 105-a may further transmit third controlsignaling 240 deactivating the set of semi-persistent SSBs and a secondCD-SSB in a third resource outside of the operating bandwidth of the UE115-a based on the third control signaling, where the CD-SSB 210 and thesecond CD-SSB are each part of a periodic set of CD-SSBs in a respectiveset of resources outside of the operating bandwidth of the UE 115-a.

In some cases, the UE 115-a may receive the NCD-SSB 225 withoutperforming radio frequency retuning between receiving the controlsignaling 220 and monitoring for the NCD-SSB 225.

In some cases, the UE 115-a may monitor, prior to receiving the controlsignaling 220, for a CD-SSB 210 that is associated with systeminformation of the cell, where the CD-SSB 310 is scheduled for receiptin the first resource. The UE 115-a may perform radio frequency retuningfrom the first resource to the operating bandwidth of the UE 115-abetween monitoring for the CD-SSB 210 and receiving the controlsignaling 220.

In some cases, the UE 115-a may perform one of a radio resourcemanagement procedure, a radio link monitoring procedure, or abidirectional forwarding detection procedure based on the monitoring ofthe NCD-SSB 225.

FIG. 3 illustrates an example of a resource diagram 300 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. In some examples, the resource diagram 300 mayimplement aspects of wireless communications systems 100 or 200.

UEs 115 operating in a reduced capability mode or an enhanced reducedcapability mode may operate within operating bandwidths 315 (e.g.,operating bandwidth 315-a, operating bandwidth 315-b, operatingbandwidth 315-c, operating bandwidth 315-d, or operating bandwidth315-e) within a carrier bandwidth 305 of a cell. A network entity 105may transmit CD-SSBs 310 that include system information for the cell.The operating bandwidth 315 of a UE 115 operating in a reducedcapability mode or an enhanced reduced capability mode may be outside ofthe frequency band in which the CD-SSB 310 is transmitted. For example,within a carrier bandwidth 305, which may span 100 MHz, a UE 115-a mayoperate within the operating bandwidth 315-b (which may span 5 MHz foran enhanced reduced capability mode, 20 MHz RF bandwidth with 4 MHzbroadband bandwidth for an enhanced reduced capability mode, or 20 MHzfor a reduced capability mode). The UE 115 operating in the operatingbandwidth 315-a may be configured with a measurement gap 330 to performRF retuning to monitor for the CD-SSB 310-a outside of the operatingbandwidth 315-a. The measurement gap 330 may be configured for periodicRF retuning if the operating bandwidth 315-a is outside of the frequencyband in which the CD-SSB 310 is transmitted and does not include aperiodic NCD-SSB. For the RF retuning, there may be a time gap betweentransmission or reception in the operating bandwidth 315-a and thereception of CD-SSB 310-a in the bandwidth 315-c. During this time gap,the UE 115 may not perform any transmission or reception using any ofthe bandwidths. The time gap can bring throughput loss to the UE 115 andthe serving network entity 105.

In some cases, the serving network entity 105 may identify that a datatransmission for the UE 115 is associated with a large payload or a lowlatency. If resources are available and the interference level isacceptable, the serving network entity 105 may transmit controlsignaling 320 dynamically enabling or scheduling an NCD-SSB 325 in theoperating bandwidth 315-a of the UE 115. For example, the controlsignaling 320 may be a DCI message. The UE 115 may skip RF retuning tothe frequency band including the CD-SSB 310-b. The NCD-SSB 325 may beused one-time or may be used for a duration of time. For example, thecontrol signaling 320 may configure a periodic or semi-persistent set ofNCD-SSBs. Reception of NCD-SSB 325 inside the operating bandwidth 315 adoes not demand any time gap, in which a UE 115 cannot perform anytransmission or reception, which provides throughput gain for the UE 115and for the serving network entity 105 as well.

In some cases, where the control signaling 320 is a DCI message, theNCD-SSB 325 position in the carrier bandwidth 305 may be pre-configuredvia RRC (e.g., other parameters may be the same as the CD-SSB 310). TheDCI message may include an information field to enable or disable theNCD-SSB. In some cases, the DCI message may include timing information(e.g., which slot or which and how many measurements the UE 115 shouldperform on the NCD-SSB 325).

In some cases, where the control signaling 320 is a DCI message, theNCD-SSB 325 position information may be scheduled by the DCI (e.g., astarting resource block of the NCD-SSB 325 may be indicated by the DCI).In some cases, the DCI message may include timing information (e.g.,which slot or which and how many measurements the UE 115 should performon the NCD-SSB 325).

In some cases, the control signaling 320 may be a group common DCImessage transmitted to UEs using the same operating bandwidth 315-a.

In some cases, the NCD-SSB 325 may be a semi-persistent NCD-SSB 325. Thecontrol signaling 320 may be transmitted via MAC signaling to enablereception at a UE 115 of the NCD-SSB 325 through the operating bandwidth315-a. A UE 115 receiving the control signaling 320 may skip RF retuningto receive the CD-SSB 310-b and instead measure the NCD-SSB 325. TheNCD-SSB 325 position in the carrier bandwidth 305 may be pre-configuredvia RRC (e.g., other parameters may be the same as the CD-SSB 310). TheNCD-SSB 325 may be used one-time or may be used for a duration of time.

In some cases, the serving network entity 105 may transmit multipledynamic NCD-SSBs 325 for multiple cells with coordination forneighboring cell measurements. The serving cell may indicate that theNCD-SSB 325 is used for the serving cell or that the NCD-SSB 325 is usedfor both the serving cell and a neighbor cell.

FIG. 4 illustrates an example of a process flow 400 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The process flow 400 may include a UE 115-b, whichmay be an example of a UE 115 as described herein. The process flow 400may include a network entity 105-b, which may be an example of a networkentity 105 as described herein. In the following description of theprocess flow 400, the operations between the network entity 105-b andthe UE 115-b may be transmitted in a different order than the exampleorder shown, or the operations performed by the network entity 105-b andthe UE 115-b may be performed in different orders or at different times.Some operations may also be omitted from the process flow 400, and otheroperations may be added to the process flow 400.

At 405, the network entity 105-b may identify an operating bandwidth forcommunications with the UE 115-b, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE 115-b, and where the first SSB is associated withsystem information of a cell that operates across a radio frequencybandwidth that includes the operating bandwidth of the UE 115-b.

In some cases, the network entity 105-b may receive, from the UE 115-b,a first control message indicating that the UE 115-b is entering areduced capability mode, and in response, the network entity 105-b maytransmit, to the UE 115-b a second control message configuring theoperating bandwidth of the UE 115-b based on the indication that the UE115-b is entering a reduced capability mode.

At 410, the network entity 105-b may transmit, to the UE 115-b, based onidentifying the operating bandwidth for communication with the UE 115-b,control signaling that schedules or enables a second SSB in a secondresource of the operating bandwidth of the UE 115-b.

At 415, the UE 115-b may monitor for, while still operating in theoperating bandwidth of the UE 115-b, for the second SSB in the secondresource based on the control signaling at 410. At 420, the networkentity 105-b may transmit the second SSB in the second resource.

In some cases, the network entity 105-b may identify that a latencytarget associated with a data transmission for the UE 115-b exceeds athreshold, and the network entity 105-b may transmit the controlsignaling at 410 based on identifying that the latency target associatedwith the data transmission for the UE 115-b exceeds the threshold.

In some cases, the network entity 105-b may identify that a payload sizeof a data transmission for the UE 115-b exceeds a threshold, and thenetwork entity 105-b may transmit the control signaling at 410 based onidentifying that the payload size of the data transmission for the UE115-b exceeds the threshold.

In some cases, transmitting the control signaling at 410 includestransmitting the control signaling via a DCI message that includes oneor more fields that schedule the second SSB on the second resource.

In some cases, transmitting the control signaling at 410 includestransmitting the control signaling via a DCI message that includes afield that enables monitoring at the UE 115-b for the second SSB, theDCI message also including scheduling information for one or more sharedchannel transmissions. In some cases, the network entity 105-b mayfurther transmit additional control signaling that schedules a frequencyposition of the second SSB within the radio frequency bandwidth, theadditional control signaling received prior to the DCI message at 410.

In some cases, transmitting the control signaling at 410 includestransmitting the control signaling via a DCI message that includes anindication of one or more measurements associated with the second SSB.

In some cases, transmitting the control signaling at 410 includestransmitting the control signaling via a group common DCI message.

In some cases, transmitting the control signaling at 410 includestransmitting the control signaling via a MAC-CE that enables monitoringat the UE 115-b for the second SSB. In some cases, the network entity105-b may further transmit second control signaling that schedules a setof semi-persistent SSBs in a respective set of resources within theoperating bandwidth of the UE 115-b, the set of semi-persistent SSBsincluding the second SSB, and the MAC-CE enabling monitoring at the UE115-b for the set of semi-persistent SSBs. In some cases, the networkentity 105-b may further transmit third control signaling deactivatingthe set of semi-persistent SSBs and a third SSB in a third resourceoutside of the operating bandwidth of the UE 115-b based on the thirdcontrol signaling, where the second SSB and the third SSB are each partof a periodic set of SSBs in a respective set of resources outside ofthe operating bandwidth of the UE 115-b.

In some cases, the first SSB may be a CD-SSB and the second SSB may bean NCD-SSB.

In some cases, the UE 115-b may receive the second SSB withoutperforming radio frequency retuning between receiving the controlsignaling at 410 and monitoring for the second SSB at 415.

In some cases, the UE 115-b may monitor, prior to receiving the controlsignaling at 410, for a third SSB that is associated with systeminformation of the cell, where the third SSB is scheduled for receipt inthe first resource. The UE 115-b may perform radio frequency retuningfrom the first resource to the operating bandwidth of the UE 115-bbetween monitoring for the third SSB and receiving the control signalingat 410.

In some cases, the UE 115-b may perform one of a radio resourcemanagement procedure, a radio link monitoring procedure, or abidirectional forwarding detection procedure based on the monitoring ofthe second SSB at 415.

FIG. 5 shows a block diagram 500 of a device 505 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The device 505 may be an example of aspects of a UE115 as described herein. The device 505 may include a receiver 510, atransmitter 515, and a communications manager 520. The device 505 mayalso include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 510 may provide a means for receiving information such aspackets, user data, control information, or any combination thereofassociated with various information channels (e.g., control channels,data channels, information channels related to configuring BWPs andSSBs). Information may be passed on to other components of the device505. The receiver 510 may utilize a single antenna or a set of multipleantennas.

The transmitter 515 may provide a means for transmitting signalsgenerated by other components of the device 505. For example, thetransmitter 515 may transmit information such as packets, user data,control information, or any combination thereof associated with variousinformation channels (e.g., control channels, data channels, informationchannels related to configuring BWPs and SSBs). In some examples, thetransmitter 515 may be co-located with a receiver 510 in a transceivermodule. The transmitter 515 may utilize a single antenna or a set ofmultiple antennas.

The communications manager 520, the receiver 510, the transmitter 515,or various combinations thereof or various components thereof may beexamples of means for performing various aspects of configuring BWPs andSSBs as described herein. For example, the communications manager 520,the receiver 510, the transmitter 515, or various combinations orcomponents thereof may support a method for performing one or more ofthe functions described herein.

In some examples, the communications manager 520, the receiver 510, thetransmitter 515, or various combinations or components thereof may beimplemented in hardware (e.g., in communications management circuitry).The hardware may include a processor, a digital signal processor (DSP),a central processing unit (CPU), an application-specific integratedcircuit (ASIC), a field-programmable gate array (FPGA) or otherprogrammable logic device, a microcontroller, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof configured as or otherwise supporting a means for performing thefunctions described in the present disclosure. In some examples, aprocessor and memory coupled with the processor may be configured toperform one or more of the functions described herein (e.g., byexecuting, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communicationsmanager 520, the receiver 510, the transmitter 515, or variouscombinations or components thereof may be implemented in code (e.g., ascommunications management software) executed by a processor. Ifimplemented in code executed by a processor, the functions of thecommunications manager 520, the receiver 510, the transmitter 515, orvarious combinations or components thereof may be performed by ageneral-purpose processor, a DSP, a CPU, a graphics processing unit(GPU), an ASIC, an FPGA, a microcontroller, or any combination of theseor other programmable logic devices (e.g., configured as or otherwisesupporting a means for performing the functions described in the presentdisclosure).

In some examples, the communications manager 520 may be configured toperform various operations (e.g., receiving, obtaining, monitoring,outputting, transmitting) using or otherwise in cooperation with thereceiver 510, the transmitter 515, or both. For example, thecommunications manager 520 may receive information from the receiver510, send information to the transmitter 515, or be integrated incombination with the receiver 510, the transmitter 515, or both toobtain information, output information, or perform various otheroperations as described herein.

The communications manager 520 may support wireless communications at aUE in accordance with examples as disclosed herein. For example, thecommunications manager 520 may be configured as or otherwise support ameans for receiving control signaling, in an operating bandwidth of theUE, that schedules or enables a first SSB in a first resource of theoperating bandwidth of the UE, the first SSB being different from asecond SSB that is associated with system information of a cell thatoperates across a radio frequency bandwidth that includes the operatingbandwidth of the UE, where the second SSB is scheduled for receipt in asecond resource that is outside of the operating bandwidth of the UE.The communications manager 520 may be configured as or otherwise supporta means for monitoring, while still operating in the operating bandwidthof the UE, for the first SSB in the first resource based on the controlsignaling.

By including or configuring the communications manager 520 in accordancewith examples as described herein, the device 505 (e.g., a processorcontrolling or otherwise coupled with the receiver 510, the transmitter515, the communications manager 520, or a combination thereof) maysupport techniques for reduced power consumption and more efficientutilization of communication resources by enabling dynamic configurationof SSBs in an operating bandwidth of a UE.

FIG. 6 shows a block diagram 600 of a device 605 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The device 605 may be an example of aspects of adevice 505 or a UE 115 as described herein. The device 605 may include areceiver 610, a transmitter 615, and a communications manager 620. Thedevice 605 may also include a processor. Each of these components may bein communication with one another (e.g., via one or more buses).

The receiver 610 may provide a means for receiving information such aspackets, user data, control information, or any combination thereofassociated with various information channels (e.g., control channels,data channels, information channels related to configuring BWPs andSSBs). Information may be passed on to other components of the device605. The receiver 610 may utilize a single antenna or a set of multipleantennas.

The transmitter 615 may provide a means for transmitting signalsgenerated by other components of the device 605. For example, thetransmitter 615 may transmit information such as packets, user data,control information, or any combination thereof associated with variousinformation channels (e.g., control channels, data channels, informationchannels related to configuring BWPs and SSBs). In some examples, thetransmitter 615 may be co-located with a receiver 610 in a transceivermodule. The transmitter 615 may utilize a single antenna or a set ofmultiple antennas.

The device 605, or various components thereof, may be an example ofmeans for performing various aspects of configuring BWPs and SSBs asdescribed herein. For example, the communications manager 620 mayinclude an SSB scheduling manager 625 an SSB monitoring manager 630, orany combination thereof. The communications manager 620 may be anexample of aspects of a communications manager 520 as described herein.In some examples, the communications manager 620, or various componentsthereof, may be configured to perform various operations (e.g.,receiving, obtaining, monitoring, outputting, transmitting) using orotherwise in cooperation with the receiver 610, the transmitter 615, orboth. For example, the communications manager 620 may receiveinformation from the receiver 610, send information to the transmitter615, or be integrated in combination with the receiver 610, thetransmitter 615, or both to obtain information, output information, orperform various other operations as described herein.

The communications manager 620 may support wireless communications at aUE in accordance with examples as disclosed herein. The SSB schedulingmanager 625 may be configured as or otherwise support a means forreceiving control signaling, in an operating bandwidth of the UE, thatschedules or enables a first SSB in a first resource of the operatingbandwidth of the UE, the first SSB being different from a second SSBthat is associated with system information of a cell that operatesacross a radio frequency bandwidth that includes the operating bandwidthof the UE, where the second SSB is scheduled for receipt in a secondresource that is outside of the operating bandwidth of the UE. The SSBmonitoring manager 630 may be configured as or otherwise support a meansfor monitoring, while still operating in the operating bandwidth of theUE, for the first SSB in the first resource based on the controlsignaling.

FIG. 7 shows a block diagram 700 of a communications manager 720 thatsupports configuring BWPs and SSBs in accordance with one or moreaspects of the present disclosure. The communications manager 720 may bean example of aspects of a communications manager 520, a communicationsmanager 620, or both, as described herein. The communications manager720, or various components thereof, may be an example of means forperforming various aspects of configuring BWPs and SSBs as describedherein. For example, the communications manager 720 may include an SSBscheduling manager 725, an SSB monitoring manager 730, an RF retuningmanager 735, a DCI manager 740, an SSB measurement manager 745, a MAC-CEmanager 750, an SSB procedure manager 755, a reduced capability manager760, an operating bandwidth manager 765, an SPS SSB scheduling manager770, or any combination thereof. Each of these components maycommunicate, directly or indirectly, with one another (e.g., via one ormore buses).

The communications manager 720 may support wireless communications at aUE in accordance with examples as disclosed herein. The SSB schedulingmanager 725 may be configured as or otherwise support a means forreceiving control signaling, in an operating bandwidth of the UE, thatschedules or enables a first SSB in a first resource of the operatingbandwidth of the UE, the first SSB being different from a second SSBthat is associated with system information of a cell that operatesacross a radio frequency bandwidth that includes the operating bandwidthof the UE, where the second SSB is scheduled for receipt in a secondresource that is outside of the operating bandwidth of the UE. The SSBmonitoring manager 730 may be configured as or otherwise support a meansfor monitoring, while still operating in the operating bandwidth of theUE, for the first SSB in the first resource based on the controlsignaling.

In some examples, the SSB monitoring manager 730 may be configured as orotherwise support a means for receiving the first SSB without performingradio frequency retuning between receiving the control signaling andmonitoring for the first SSB.

In some examples, the SSB monitoring manager 730 may be configured as orotherwise support a means for monitoring, prior to receiving the controlsignaling, for a third SSB that is associated with system information ofthe cell, where the third SSB is scheduled for receipt in the secondresource. In some examples, the RF retuning manager 735 may beconfigured as or otherwise support a means for performing radiofrequency retuning from the second resource to the operating bandwidthof the UE between monitoring for the third SSB and receiving the controlsignaling.

In some examples, to support receiving the control signaling, the DCImanager 740 may be configured as or otherwise support a means forreceiving the control signaling via a DCI message that includes one ormore fields that schedule the first SSB on the first resource.

In some examples, to support receiving the control signaling, the DCImanager 740 may be configured as or otherwise support a means forreceiving the control signaling via a DCI message that includes a fieldthat enables the monitoring for the first SSB, the DCI message alsoincluding scheduling information for one or more shared channeltransmissions.

In some examples, the SSB scheduling manager 725 may be configured as orotherwise support a means for receiving additional control signalingthat schedules a frequency position of the first SSB within the radiofrequency bandwidth, the additional control signaling received prior tothe DCI message.

In some examples, to support receiving the control signaling, the SSBmeasurement manager 745 may be configured as or otherwise support ameans for receiving the control signaling via a DCI message thatincludes an indication of one or more measurements associated with thefirst SSB.

In some examples, to support receiving the control signaling, the DCImanager 740 may be configured as or otherwise support a means forreceiving the control signaling via a group common DCI message.

In some examples, to support receiving the control signaling, the MAC-CEmanager 750 may be configured as or otherwise support a means forreceiving the control signaling via a MAC-CE that enables the monitoringfor the first SSB.

In some examples, the SPS SSB scheduling manager 770 may be configuredas or otherwise support a means for receiving second control signalingthat schedules a set of semi-persistent SSBs in a respective set ofresources within the operating bandwidth of the UE, the set ofsemi-persistent SSBs including the first SSB, and the MAC-CE enablingthe monitoring for the set of semi-persistent SSBs.

In some examples, the SPS SSB scheduling manager 770 may be configuredas or otherwise support a means for receiving third control signalingdeactivating the set of semi-persistent SSBs. In some examples, the SSBmonitoring manager 730 may be configured as or otherwise support a meansfor monitoring for a third SSB in a third resource outside of theoperating bandwidth of the UE based on the third control signaling,where the second SSB and the third SSB are each part of a periodic setof SSBs in a respective set of resources outside of the operatingbandwidth of the UE.

In some examples, the SSB procedure manager 755 may be configured as orotherwise support a means for performing one of a radio resourcemanagement procedure, a radio link monitoring procedure, or abidirectional forwarding detection procedure based on the monitoring ofthe first SSB.

In some examples, the second SSB includes a cell-defining SSB and thefirst SSB includes anon-cell-defining SSB.

In some examples, the reduced capability manager 760 may be configuredas or otherwise support a means for transmitting, to a network entity, afirst control message indicating that the UE is entering a reducedcapability mode. In some examples, the operating bandwidth manager 765may be configured as or otherwise support a means for receiving, fromthe network entity, a second control message configuring the operatingbandwidth of the UE based on the first control message.

FIG. 8 shows a diagram of a system 800 including a device 805 thatsupports configuring BWPs and SSBs in accordance with one or moreaspects of the present disclosure. The device 805 may be an example ofor include the components of a device 505, a device 605, or a UE 115 asdescribed herein. The device 805 may communicate (e.g., wirelessly) withone or more network entities 105, one or more UEs 115, or anycombination thereof. The device 805 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, such as a communicationsmanager 820, an input/output (I/O) controller 810, a transceiver 815, anantenna 825, a memory 830, code 835, and a processor 840. Thesecomponents may be in electronic communication or otherwise coupled(e.g., operatively, communicatively, functionally, electronically,electrically) via one or more buses (e.g., a bus 845).

The I/O controller 810 may manage input and output signals for thedevice 805. The I/O controller 810 may also manage peripherals notintegrated into the device 805. In some cases, the I/O controller 810may represent a physical connection or port to an external peripheral.In some cases, the I/O controller 810 may utilize an operating systemsuch as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®), oranother known operating system. Additionally, or alternatively, the I/Ocontroller 810 may represent or interact with a modem, a keyboard, amouse, a touchscreen, or a similar device. In some cases, the I/Ocontroller 810 may be implemented as part of a processor, such as theprocessor 840. In some cases, a user may interact with the device 805via the I/O controller 810 or via hardware components controlled by theI/O controller 810.

In some cases, the device 805 may include a single antenna 825. However,in some other cases, the device 805 may have more than one antenna 825,which may be capable of concurrently transmitting or receiving multiplewireless transmissions. The transceiver 815 may communicatebi-directionally, via the one or more antennas 825, wired, or wirelesslinks as described herein. For example, the transceiver 815 mayrepresent a wireless transceiver and may communicate bi-directionallywith another wireless transceiver. The transceiver 815 may also includea modem to modulate the packets, to provide the modulated packets to oneor more antennas 825 for transmission, and to demodulate packetsreceived from the one or more antennas 825. The transceiver 815, or thetransceiver 815 and one or more antennas 825, may be an example of atransmitter 515, a transmitter 615, a receiver 510, a receiver 610, orany combination thereof or component thereof, as described herein.

The memory 830 may include random access memory (RAM) and read-onlymemory (ROM). The memory 830 may store computer-readable,computer-executable code 835 including instructions that, when executedby the processor 840, cause the device 805 to perform various functionsdescribed herein. The code 835 may be stored in a non-transitorycomputer-readable medium such as system memory or another type ofmemory. In some cases, the code 835 may not be directly executable bythe processor 840 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein. In some cases, thememory 830 may contain, among other things, a basic I/O system (BIOS)which may control basic hardware or software operation such as theinteraction with peripheral components or devices.

The processor 840 may include an intelligent hardware device (e.g., ageneral-purpose processor, a DSP, a CPU, a GPU, a microcontroller, anASIC, an FPGA, a programmable logic device, a discrete gate ortransistor logic component, a discrete hardware component, or anycombination thereof). In some cases, the processor 840 may be configuredto operate a memory array using a memory controller. In some othercases, a memory controller may be integrated into the processor 840. Theprocessor 840 may be configured to execute computer-readableinstructions stored in a memory (e.g., the memory 830) to cause thedevice 805 to perform various functions (e.g., functions or taskssupporting configuring BWPs and SSBs). For example, the device 805 or acomponent of the device 805 may include a processor 840 and memory 830coupled with or to the processor 840, the processor 840 and memory 830configured to perform various functions described herein.

The communications manager 820 may support wireless communications at aUE in accordance with examples as disclosed herein. For example, thecommunications manager 820 may be configured as or otherwise support ameans for receiving control signaling, in an operating bandwidth of theUE, that schedules or enables a first SSB in a first resource of theoperating bandwidth of the UE, the first SSB being different from asecond SSB that is associated with system information of a cell thatoperates across a radio frequency bandwidth that includes the operatingbandwidth of the UE, where the second SSB is scheduled for receipt in asecond resource that is outside of the operating bandwidth of the UE.The communications manager 820 may be configured as or otherwise supporta means for monitoring, while still operating in the operating bandwidthof the UE, for the first SSB in the first resource based on the controlsignaling.

By including or configuring the communications manager 820 in accordancewith examples as described herein, the device 805 may support techniquesfor reduced power consumption, more efficient utilization ofcommunication resources, improved coordination between devices, andlonger battery life by enabling dynamic configuration of SSBs in anoperating bandwidth of a UE.

In some examples, the communications manager 820 may be configured toperform various operations (e.g., receiving, monitoring, transmitting)using or otherwise in cooperation with the transceiver 815, the one ormore antennas 825, or any combination thereof. Although thecommunications manager 820 is illustrated as a separate component, insome examples, one or more functions described with reference to thecommunications manager 820 may be supported by or performed by theprocessor 840, the memory 830, the code 835, or any combination thereof.For example, the code 835 may include instructions executable by theprocessor 840 to cause the device 805 to perform various aspects ofconfiguring BWPs and SSBs as described herein, or the processor 840 andthe memory 830 may be otherwise configured to perform or support suchoperations.

FIG. 9 shows a block diagram 900 of a device 905 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The device 905 may be an example of aspects of anetwork entity 105 as described herein. The device 905 may include areceiver 910, a transmitter 915, and a communications manager 920. Thedevice 905 may also include a processor. Each of these components may bein communication with one another (e.g., via one or more buses).

The receiver 910 may provide a means for obtaining (e.g., receiving,determining, identifying) information such as user data, controlinformation, or any combination thereof (e.g., I/Q samples, symbols,packets, protocol data units, service data units) associated withvarious channels (e.g., control channels, data channels, informationchannels, channels associated with a protocol stack). Information may bepassed on to other components of the device 905. In some examples, thereceiver 910 may support obtaining information by receiving signals viaone or more antennas. Additionally, or alternatively, the receiver 910may support obtaining information by receiving signals via one or morewired (e.g., electrical, fiber optic) interfaces, wireless interfaces,or any combination thereof.

The transmitter 915 may provide a means for outputting (e.g.,transmitting, providing, conveying, sending) information generated byother components of the device 905. For example, the transmitter 915 mayoutput information such as user data, control information, or anycombination thereof (e.g., I/Q samples, symbols, packets, protocol dataunits, service data units) associated with various channels (e.g.,control channels, data channels, information channels, channelsassociated with a protocol stack). In some examples, the transmitter 915may support outputting information by transmitting signals via one ormore antennas. Additionally, or alternatively, the transmitter 915 maysupport outputting information by transmitting signals via one or morewired (e.g., electrical, fiber optic) interfaces, wireless interfaces,or any combination thereof. In some examples, the transmitter 915 andthe receiver 910 may be co-located in a transceiver, which may includeor be coupled with a modem.

The communications manager 920, the receiver 910, the transmitter 915,or various combinations thereof or various components thereof may beexamples of means for performing various aspects of configuring BWPs andSSBs as described herein. For example, the communications manager 920,the receiver 910, the transmitter 915, or various combinations orcomponents thereof may support a method for performing one or more ofthe functions described herein.

In some examples, the communications manager 920, the receiver 910, thetransmitter 915, or various combinations or components thereof may beimplemented in hardware (e.g., in communications management circuitry).The hardware may include a processor, a DSP, a CPU, a GPU, an ASIC, anFPGA or other programmable logic device, a microcontroller, discretegate or transistor logic, discrete hardware components, or anycombination thereof configured as or otherwise supporting a means forperforming the functions described in the present disclosure. In someexamples, a processor and memory coupled with the processor may beconfigured to perform one or more of the functions described herein(e.g., by executing, by the processor, instructions stored in thememory).

Additionally, or alternatively, in some examples, the communicationsmanager 920, the receiver 910, the transmitter 915, or variouscombinations or components thereof may be implemented in code (e.g., ascommunications management software) executed by a processor. Ifimplemented in code executed by a processor, the functions of thecommunications manager 920, the receiver 910, the transmitter 915, orvarious combinations or components thereof may be performed by ageneral-purpose processor, a DSP, a GPU, a CPU, an ASIC, an FPGA, amicrocontroller, or any combination of these or other programmable logicdevices (e.g., configured as or otherwise supporting a means forperforming the functions described in the present disclosure).

In some examples, the communications manager 920 may be configured toperform various operations (e.g., receiving, obtaining, monitoring,outputting, transmitting) using or otherwise in cooperation with thereceiver 910, the transmitter 915, or both. For example, thecommunications manager 920 may receive information from the receiver910, send information to the transmitter 915, or be integrated incombination with the receiver 910, the transmitter 915, or both toobtain information, output information, or perform various otheroperations as described herein.

The communications manager 920 may support wireless communications at anetwork entity in accordance with examples as disclosed herein. Forexample, the communications manager 920 may be configured as orotherwise support a means for identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The communicationsmanager 920 may be configured as or otherwise support a means fortransmitting, based on identifying the operating bandwidth forcommunications with the UE, control signaling that schedules or enablesa second SSB in a second resource of the operating bandwidth of the UE.The communications manager 920 may be configured as or otherwise supporta means for transmitting the second SSB in the second resource.

By including or configuring the communications manager 920 in accordancewith examples as described herein, the device 905 (e.g., a processorcontrolling or otherwise coupled with the receiver 910, the transmitter915, the communications manager 920, or a combination thereof) maysupport techniques for reduced power consumption and more efficientutilization of communication resources by enabling dynamic configurationof SSBs in an operating bandwidth of a UE.

FIG. 10 shows a block diagram 1000 of a device 1005 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The device 1005 may be an example of aspects of adevice 905 or a network entity 105 as described herein. The device 1005may include a receiver 1010, a transmitter 1015, and a communicationsmanager 1020. The device 1005 may also include a processor. Each ofthese components may be in communication with one another (e.g., via oneor more buses).

The receiver 1010 may provide a means for obtaining (e.g., receiving,determining, identifying) information such as user data, controlinformation, or any combination thereof (e.g., I/Q samples, symbols,packets, protocol data units, service data units) associated withvarious channels (e.g., control channels, data channels, informationchannels, channels associated with a protocol stack). Information may bepassed on to other components of the device 1005. In some examples, thereceiver 1010 may support obtaining information by receiving signals viaone or more antennas. Additionally, or alternatively, the receiver 1010may support obtaining information by receiving signals via one or morewired (e.g., electrical, fiber optic) interfaces, wireless interfaces,or any combination thereof.

The transmitter 1015 may provide a means for outputting (e.g.,transmitting, providing, conveying, sending) information generated byother components of the device 1005. For example, the transmitter 1015may output information such as user data, control information, or anycombination thereof (e.g., I/Q samples, symbols, packets, protocol dataunits, service data units) associated with various channels (e.g.,control channels, data channels, information channels, channelsassociated with a protocol stack). In some examples, the transmitter1015 may support outputting information by transmitting signals via oneor more antennas. Additionally, or alternatively, the transmitter 1015may support outputting information by transmitting signals via one ormore wired (e.g., electrical, fiber optic) interfaces, wirelessinterfaces, or any combination thereof. In some examples, thetransmitter 1015 and the receiver 1010 may be co-located in atransceiver, which may include or be coupled with a modem.

The device 1005, or various components thereof, may be an example ofmeans for performing various aspects of configuring BWPs and SSBs asdescribed herein. For example, the communications manager 1020 mayinclude a UE operating bandwidth manager 1025, an SSB scheduling manager1030, an SSB transmission manager 1035, or any combination thereof. Thecommunications manager 1020 may be an example of aspects of acommunications manager 920 as described herein. In some examples, thecommunications manager 1020, or various components thereof, may beconfigured to perform various operations (e.g., receiving, obtaining,monitoring, outputting, transmitting) using or otherwise in cooperationwith the receiver 1010, the transmitter 1015, or both. For example, thecommunications manager 1020 may receive information from the receiver1010, send information to the transmitter 1015, or be integrated incombination with the receiver 1010, the transmitter 1015, or both toobtain information, output information, or perform various otheroperations as described herein.

The communications manager 1020 may support wireless communications at anetwork entity in accordance with examples as disclosed herein. The UEoperating bandwidth manager 1025 may be configured as or otherwisesupport a means for identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The SSB schedulingmanager 1030 may be configured as or otherwise support a means fortransmitting, based on identifying the operating bandwidth forcommunications with the UE, control signaling that schedules or enablesa second SSB in a second resource of the operating bandwidth of the UE.The SSB transmission manager 1035 may be configured as or otherwisesupport a means for transmitting the second SSB in the second resource.

FIG. 11 shows a block diagram 1100 of a communications manager 1120 thatsupports configuring BWPs and SSBs in accordance with one or moreaspects of the present disclosure. The communications manager 1120 maybe an example of aspects of a communications manager 920, acommunications manager 1020, or both, as described herein. Thecommunications manager 1120, or various components thereof, may be anexample of means for performing various aspects of configuring BWPs andSSBs as described herein. For example, the communications manager 1120may include a UE operating bandwidth manager 1125, an SSB schedulingmanager 1130, an SSB transmission manager 1135, a latency target manager1140, a payload size manager 1145, a DCI manager 1150, an SSBmeasurement manager 1155, a MAC-CE manager 1160, a reduced capability UEmanager 1165, an SPS SSB scheduling manager 1170, or any combinationthereof. Each of these components may communicate, directly orindirectly, with one another (e.g., via one or more buses) which mayinclude communications within a protocol layer of a protocol stack,communications associated with a logical channel of a protocol stack(e.g., between protocol layers of a protocol stack, within a device,component, or virtualized component associated with a network entity105, between devices, components, or virtualized components associatedwith a network entity 105), or any combination thereof.

The communications manager 1120 may support wireless communications at anetwork entity in accordance with examples as disclosed herein. The UEoperating bandwidth manager 1125 may be configured as or otherwisesupport a means for identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The SSB schedulingmanager 1130 may be configured as or otherwise support a means fortransmitting, based on identifying the operating bandwidth forcommunications with the UE, control signaling that schedules or enablesa second SSB in a second resource of the operating bandwidth of the UE.The SSB transmission manager 1135 may be configured as or otherwisesupport a means for transmitting the second SSB in the second resource.

In some examples, the latency target manager 1140 may be configured asor otherwise support a means for identifying that a latency targetassociated with a data transmission for the UE exceeds a threshold,where transmitting the control signaling is based on the identifying.

In some examples, the payload size manager 1145 may be configured as orotherwise support a means for identifying that a payload size associatedwith a data transmission for the UE exceeds a threshold, wheretransmitting the control signaling is based on the identifying.

In some examples, to support transmitting the control signaling, the DCImanager 1150 may be configured as or otherwise support a means fortransmitting the control signaling via a DCI message that includes oneor more fields that schedule the second SSB on the second resource.

In some examples, to support transmitting the control signaling, the DCImanager 1150 may be configured as or otherwise support a means fortransmitting the control signaling via a DCI message that includes afield that enables monitoring at the UE for the second SSB, the DCImessage also including scheduling information for one or more sharedchannel transmissions.

In some examples, the SSB scheduling manager 1130 may be configured asor otherwise support a means for transmitting additional controlsignaling that schedules a frequency position of the second SSB withinthe radio frequency bandwidth, the additional control signaling receivedprior to the DCI message.

In some examples, to support transmitting the control signaling, the SSBmeasurement manager 1155 may be configured as or otherwise support ameans for transmitting the control signaling via a DCI message thatincludes an indication of one or more measurements associated with thesecond SSB.

In some examples, to support transmitting the control signaling, the DCImanager 1150 may be configured as or otherwise support a means fortransmitting the control signaling via a group common DCI message.

In some examples, to support transmitting the control signaling, theMAC-CE manager 1160 may be configured as or otherwise support a meansfor transmitting the control signaling via a MAC-CE that enablesmonitoring at the UE for the second SSB.

In some examples, the SPS SSB scheduling manager 1170 may be configuredas or otherwise support a means for transmitting second controlsignaling that schedules a set of semi-persistent SSBs in a respectiveset of resources within the operating bandwidth of the UE, the set ofsemi-persistent SSBs including the second SSB, and the MAC-CE enablingmonitoring at the UE for the set of semi-persistent SSBs.

In some examples, the SPS SSB scheduling manager 1170 may be configuredas or otherwise support a means for transmitting third control signalingdeactivating the set of semi-persistent SSBs. In some examples, the SSBtransmission manager 1135 may be configured as or otherwise support ameans for transmitting a third SSB in a third resource outside of theoperating bandwidth of the UE based on the third control signaling,where the second SSB and the third SSB are each part of a periodic setof SSBs in a respective set of resources outside of the operatingbandwidth of the UE.

In some examples, the first SSB includes a cell-defining SSB and thesecond SSB includes a non-cell-defining SSB.

In some examples, the reduced capability UE manager 1165 may beconfigured as or otherwise support a means for receiving, from the UE, afirst control message indicating that the UE is entering a reducedcapability mode. In some examples, the UE operating bandwidth manager1125 may be configured as or otherwise support a means for transmitting,to the UE, a second control message configuring the operating bandwidthof the UE based on the first control message.

FIG. 12 shows a diagram of a system 1200 including a device 1205 thatsupports configuring BWPs and SSBs in accordance with one or moreaspects of the present disclosure. The device 1205 may be an example ofor include the components of a device 905, a device 1005, or a networkentity 105 as described herein. The device 1205 may communicate with oneor more network entities 105, one or more UEs 115, or any combinationthereof, which may include communications over one or more wiredinterfaces, over one or more wireless interfaces, or any combinationthereof. The device 1205 may include components that support outputtingand obtaining communications, such as a communications manager 1220, atransceiver 1210, an antenna 1215, a memory 1225, code 1230, and aprocessor 1235. These components may be in electronic communication orotherwise coupled (e.g., operatively, communicatively, functionally,electronically, electrically) via one or more buses (e.g., a bus 1240).

The transceiver 1210 may support bi-directional communications via wiredlinks, wireless links, or both as described herein. In some examples,the transceiver 1210 may include a wired transceiver and may communicatebi-directionally with another wired transceiver. Additionally, oralternatively, in some examples, the transceiver 1210 may include awireless transceiver and may communicate bi-directionally with anotherwireless transceiver. In some examples, the device 1205 may include oneor more antennas 1215, which may be capable of transmitting or receivingwireless transmissions (e.g., concurrently). The transceiver 1210 mayalso include a modem to modulate signals, to provide the modulatedsignals for transmission (e.g., by one or more antennas 1215, by a wiredtransmitter), to receive modulated signals (e.g., from one or moreantennas 1215, from a wired receiver), and to demodulate signals. Thetransceiver 1210, or the transceiver 1210 and one or more antennas 1215or wired interfaces, where applicable, may be an example of atransmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, orany combination thereof or component thereof, as described herein. Insome examples, the transceiver may be operable to support communicationsvia one or more communications links (e.g., a communication link 125, abackhaul communication link 120, a midhaul communication link 162, afronthaul communication link 168).

The memory 1225 may include RAM and ROM. The memory 1225 may storecomputer-readable, computer-executable code 1230 including instructionsthat, when executed by the processor 1235, cause the device 1205 toperform various functions described herein. The code 1230 may be storedin a non-transitory computer-readable medium such as system memory oranother type of memory. In some cases, the code 1230 may not be directlyexecutable by the processor 1235 but may cause a computer (e.g., whencompiled and executed) to perform functions described herein. In somecases, the memory 1225 may contain, among other things, a BIOS which maycontrol basic hardware or software operation such as the interactionwith peripheral components or devices.

The processor 1235 may include an intelligent hardware device (e.g., ageneral-purpose processor, a DSP, a GPU, an ASIC, a CPU, an FPGA, amicrocontroller, a programmable logic device, discrete gate ortransistor logic, a discrete hardware component, or any combinationthereof). In some cases, the processor 1235 may be configured to operatea memory array using a memory controller. In some other cases, a memorycontroller may be integrated into the processor 1235. The processor 1235may be configured to execute computer-readable instructions stored in amemory (e.g., the memory 1225) to cause the device 1205 to performvarious functions (e.g., functions or tasks supporting configuring BWPsand SSBs). For example, the device 1205 or a component of the device1205 may include a processor 1235 and memory 1225 coupled with theprocessor 1235, the processor 1235 and memory 1225 configured to performvarious functions described herein. The processor 1235 may be an exampleof a cloud-computing platform (e.g., one or more physical nodes andsupporting software such as operating systems, virtual machines, orcontainer instances) that may host the functions (e.g., by executingcode 1230) to perform the functions of the device 1205.

In some examples, a bus 1240 may support communications of (e.g.,within) a protocol layer of a protocol stack. In some examples, a bus1240 may support communications associated with a logical channel of aprotocol stack (e.g., between protocol layers of a protocol stack),which may include communications performed within a component of thedevice 1205, or between different components of the device 1205 that maybe co-located or located in different locations (e.g., where the device1205 may refer to a system in which one or more of the communicationsmanager 1220, the transceiver 1210, the memory 1225, the code 1230, andthe processor 1235 may be located in one of the different components ordivided between different components).

In some examples, the communications manager 1220 may manage aspects ofcommunications with a core network 130 (e.g., via one or more wired orwireless backhaul links). For example, the communications manager 1220may manage the transfer of data communications for client devices, suchas one or more UEs 115. In some examples, the communications manager1220 may manage communications with other network entities 105, and mayinclude a controller or scheduler for controlling communications withUEs 115 in cooperation with other network entities 105. In someexamples, the communications manager 1220 may support an X2 interfacewithin an LTE/LTE-A wireless communications network technology toprovide communication between network entities 105.

The communications manager 1220 may support wireless communications at anetwork entity in accordance with examples as disclosed herein. Forexample, the communications manager 1220 may be configured as orotherwise support a means for identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The communicationsmanager 1220 may be configured as or otherwise support a means fortransmitting, based on identifying the operating bandwidth forcommunications with the UE, control signaling that schedules or enablesa second SSB in a second resource of the operating bandwidth of the UE.The communications manager 1220 may be configured as or otherwisesupport a means for transmitting the second SSB in the second resource.

By including or configuring the communications manager 1220 inaccordance with examples as described herein, the device 1205 maysupport techniques for reduced power consumption, more efficientutilization of communication resources, improved coordination betweendevices, and longer battery life by enabling dynamic configuration ofSSBs in an operating bandwidth of a UE.

In some examples, the communications manager 1220 may be configured toperform various operations (e.g., receiving, obtaining, monitoring,outputting, transmitting) using or otherwise in cooperation with thetransceiver 1210, the one or more antennas 1215 (e.g., whereapplicable), or any combination thereof. Although the communicationsmanager 1220 is illustrated as a separate component, in some examples,one or more functions described with reference to the communicationsmanager 1220 may be supported by or performed by the processor 1235, thememory 1225, the code 1230, the transceiver 1210, or any combinationthereof. For example, the code 1230 may include instructions executableby the processor 1235 to cause the device 1205 to perform variousaspects of configuring BWPs and SSBs as described herein, or theprocessor 1235 and the memory 1225 may be otherwise configured toperform or support such operations.

FIG. 13 shows a flowchart illustrating a method 1300 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 1300 may be implementedby a UE or its components as described herein. For example, theoperations of the method 1300 may be performed by a UE 115 as describedwith reference to FIGS. 1 through 8 . In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the described functions. Additionally, or alternatively, the UEmay perform aspects of the described functions using special-purposehardware.

At 1305, the method may include receiving control signaling, in anoperating bandwidth of the UE, that schedules or enables a first SSB ina first resource of the operating bandwidth of the UE, the first SSBbeing different from a second SSB that is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, where the second SSB isscheduled for receipt in a second resource that is outside of theoperating bandwidth of the UE. The operations of 1305 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1305 may be performed by an SSB schedulingmanager 725 as described with reference to FIG. 7 .

At 1310, the method may include monitoring, while still operating in theoperating bandwidth of the UE, for the first SSB in the first resourcebased on the control signaling. The operations of 1310 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1310 may be performed by an SSB monitoringmanager 730 as described with reference to FIG. 7 .

FIG. 14 shows a flowchart illustrating a method 1400 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 1400 may be implementedby a UE or its components as described herein. For example, theoperations of the method 1400 may be performed by a UE 115 as describedwith reference to FIGS. 1 through 8 . In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the described functions. Additionally, or alternatively, the UEmay perform aspects of the described functions using special-purposehardware.

At 1405, the method may include receiving control signaling, in anoperating bandwidth of the UE, that schedules or enables a first SSB ina first resource of the operating bandwidth of the UE, the first SSBbeing different from a second SSB that is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, where the second SSB isscheduled for receipt in a second resource that is outside of theoperating bandwidth of the UE. The operations of 1405 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1405 may be performed by an SSB schedulingmanager 725 as described with reference to FIG. 7 .

At 1410, the method may include monitoring, while still operating in theoperating bandwidth of the UE, for the first SSB in the first resourcebased on the control signaling. The operations of 1410 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1410 may be performed by an SSB monitoringmanager 730 as described with reference to FIG. 7 .

At 1415, the method may include receiving the first SSB withoutperforming radio frequency retuning between receiving the controlsignaling and monitoring for the first SSB. The operations of 1415 maybe performed in accordance with examples as disclosed herein. In someexamples, aspects of the operations of 1415 may be performed by an SSBmonitoring manager 730 as described with reference to FIG. 7 .

FIG. 15 shows a flowchart illustrating a method 1500 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 1500 may be implementedby a UE or its components as described herein. For example, theoperations of the method 1500 may be performed by a UE 115 as describedwith reference to FIGS. 1 through 8 . In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the described functions. Additionally, or alternatively, the UEmay perform aspects of the described functions using special-purposehardware.

At 1505, the method may include receiving control signaling, in anoperating bandwidth of the UE, that schedules or enables a first SSB ina first resource of the operating bandwidth of the UE, the first SSBbeing different from a second SSB that is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, where the second SSB isscheduled for receipt in a second resource that is outside of theoperating bandwidth of the UE. The operations of 1505 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1505 may be performed by an SSB schedulingmanager 725 as described with reference to FIG. 7 .

At 1510, the method may include monitoring, while still operating in theoperating bandwidth of the UE, for the first SSB in the first resourcebased on the control signaling. The operations of 1510 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1510 may be performed by an SSB monitoringmanager 730 as described with reference to FIG. 7 .

FIG. 16 shows a flowchart illustrating a method 1600 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 1600 may be implementedby a UE or its components as described herein. For example, theoperations of the method 1600 may be performed by a UE 115 as describedwith reference to FIGS. 1 through 8 . In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the described functions. Additionally, or alternatively, the UEmay perform aspects of the described functions using special-purposehardware.

At 1605, the method may include receiving control signaling, in anoperating bandwidth of the UE, that schedules or enables a first SSB ina first resource of the operating bandwidth of the UE, the first SSBbeing different from a second SSB that is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, where the second SSB isscheduled for receipt in a second resource that is outside of theoperating bandwidth of the UE. The operations of 1605 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1605 may be performed by an SSB schedulingmanager 725 as described with reference to FIG. 7 .

At 1610, the method may include receiving the control signaling via aDCI message that includes one or more fields that schedule the first SSBon the first resource. The operations of 1610 may be performed inaccordance with examples as disclosed herein. In some examples, aspectsof the operations of 1610 may be performed by a DCI manager 740 asdescribed with reference to FIG. 7 .

At 1615, the method may include monitoring, while still operating in theoperating bandwidth of the UE, for the first SSB in the first resourcebased on the control signaling. The operations of 1615 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1615 may be performed by an SSB monitoringmanager 730 as described with reference to FIG. 7 .

FIG. 17 shows a flowchart illustrating a method 1700 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 1700 may be implementedby a UE or its components as described herein. For example, theoperations of the method 1700 may be performed by a UE 115 as describedwith reference to FIGS. 1 through 8 . In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the described functions. Additionally, or alternatively, the UEmay perform aspects of the described functions using special-purposehardware.

At 1705, the method may include receiving control signaling, in anoperating bandwidth of the UE, that schedules or enables a first SSB ina first resource of the operating bandwidth of the UE, the first SSBbeing different from a second SSB that is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE, where the second SSB isscheduled for receipt in a second resource that is outside of theoperating bandwidth of the UE. The operations of 1705 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1705 may be performed by an SSB schedulingmanager 725 as described with reference to FIG. 7 .

At 1710, the method may include receiving the control signaling via aDCI message that includes a field that enables the monitoring for thefirst SSB, the DCI message also including scheduling information for oneor more shared channel transmissions. The operations of 1710 may beperformed in accordance with examples as disclosed herein. In someexamples, aspects of the operations of 1710 may be performed by a DCImanager 740 as described with reference to FIG. 7 .

At 1715, the method may include monitoring, while still operating in theoperating bandwidth of the UE, for the first SSB in the first resourcebased on the control signaling. The operations of 1715 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1715 may be performed by an SSB monitoringmanager 730 as described with reference to FIG. 7 .

FIG. 18 shows a flowchart illustrating a method 1800 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 1800 may be implementedby a network entity or its components as described herein. For example,the operations of the method 1800 may be performed by a network entityas described with reference to FIGS. 1 through 4 and 9 through 12 . Insome examples, a network entity may execute a set of instructions tocontrol the functional elements of the network entity to perform thedescribed functions. Additionally, or alternatively, the network entitymay perform aspects of the described functions using special-purposehardware.

At 1805, the method may include identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The operations of 1805may be performed in accordance with examples as disclosed herein. Insome examples, aspects of the operations of 1805 may be performed by aUE operating bandwidth manager 1125 as described with reference to FIG.11 .

At 1810, the method may include transmitting, based on identifying theoperating bandwidth for communications with the UE, control signalingthat schedules or enables a second SSB in a second resource of theoperating bandwidth of the UE. The operations of 1810 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 1810 may be performed by an SSB schedulingmanager 1130 as described with reference to FIG. 11 .

At 1815, the method may include transmitting the second SSB in thesecond resource. The operations of 1815 may be performed in accordancewith examples as disclosed herein. In some examples, aspects of theoperations of 1815 may be performed by an SSB transmission manager 1135as described with reference to FIG. 11 .

FIG. 19 shows a flowchart illustrating a method 1900 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 1900 may be implementedby a network entity or its components as described herein. For example,the operations of the method 1900 may be performed by a network entityas described with reference to FIGS. 1 through 4 and 9 through 12 . Insome examples, a network entity may execute a set of instructions tocontrol the functional elements of the network entity to perform thedescribed functions. Additionally, or alternatively, the network entitymay perform aspects of the described functions using special-purposehardware.

At 1905, the method may include identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The operations of 1905may be performed in accordance with examples as disclosed herein. Insome examples, aspects of the operations of 1905 may be performed by aUE operating bandwidth manager 1125 as described with reference to FIG.11 .

At 1910, the method may include identifying that a latency targetassociated with a data transmission for the UE exceeds a threshold. Theoperations of 1910 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 1910may be performed by a latency target manager 1140 as described withreference to FIG. 11 .

At 1915, the method may include transmitting, based on identifying theoperating bandwidth for communications with the UE, control signalingthat schedules or enables a second SSB in a second resource of theoperating bandwidth of the UE, where transmitting the control signalingis based at least in part on the identifying that the latency targetassociated with the data transmission for the UE exceeds the threshold.The operations of 1915 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 1915may be performed by an SSB scheduling manager 1130 as described withreference to FIG. 11 .

At 1920, the method may include transmitting the second SSB in thesecond resource. The operations of 1920 may be performed in accordancewith examples as disclosed herein. In some examples, aspects of theoperations of 1920 may be performed by an SSB transmission manager 1135as described with reference to FIG. 11 .

FIG. 20 shows a flowchart illustrating a method 2000 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 2000 may be implementedby a network entity or its components as described herein. For example,the operations of the method 2000 may be performed by a network entityas described with reference to FIGS. 1 through 4 and 9 through 12. Insome examples, a network entity may execute a set of instructions tocontrol the functional elements of the network entity to perform thedescribed functions. Additionally, or alternatively, the network entitymay perform aspects of the described functions using special-purposehardware.

At 2005, the method may include identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The operations of 2005may be performed in accordance with examples as disclosed herein. Insome examples, aspects of the operations of 2005 may be performed by aUE operating bandwidth manager 1125 as described with reference to FIG.11 .

At 2010, the method may include identifying that a payload sizeassociated with a data transmission for the UE exceeds a threshold. Theoperations of 2010 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 2010may be performed by a payload size manager 1145 as described withreference to FIG. 11 .

At 2015, the method may include transmitting, based on identifying theoperating bandwidth for communications with the UE, control signalingthat schedules or enables a second SSB in a second resource of theoperating bandwidth of the UE, where transmitting the control signalingis based at least in part on the identifying that the payload sizeassociated with the data transmission for the UE exceeds the threshold.The operations of 2015 may be performed in accordance with examples asdisclosed herein. In some examples, aspects of the operations of 2015may be performed by an SSB scheduling manager 1130 as described withreference to FIG. 11 .

At 2020, the method may include transmitting the second SSB in thesecond resource. The operations of 2020 may be performed in accordancewith examples as disclosed herein. In some examples, aspects of theoperations of 2020 may be performed by an SSB transmission manager 1135as described with reference to FIG. 11 .

FIG. 21 shows a flowchart illustrating a method 2100 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 2100 may be implementedby a network entity or its components as described herein. For example,the operations of the method 2100 may be performed by a network entityas described with reference to FIGS. 1 through 4 and 9 through 12 . Insome examples, a network entity may execute a set of instructions tocontrol the functional elements of the network entity to perform thedescribed functions. Additionally, or alternatively, the network entitymay perform aspects of the described functions using special-purposehardware.

At 2105, the method may include identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The operations of 2105may be performed in accordance with examples as disclosed herein. Insome examples, aspects of the operations of 2105 may be performed by aUE operating bandwidth manager 1125 as described with reference to FIG.11 .

At 2110, the method may include transmitting, based on identifying theoperating bandwidth for communications with the UE, control signalingthat schedules or enables a second SSB in a second resource of theoperating bandwidth of the UE. The operations of 2110 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 2110 may be performed by an SSB schedulingmanager 1130 as described with reference to FIG. 11 .

At 2115, the method may include transmitting the control signaling via aDCI message that includes one or more fields that schedule the secondSSB on the second resource. The operations of 2115 may be performed inaccordance with examples as disclosed herein. In some examples, aspectsof the operations of 2115 may be performed by a DCI manager 1150 asdescribed with reference to FIG. 11 .

At 2120, the method may include transmitting the second SSB in thesecond resource. The operations of 2120 may be performed in accordancewith examples as disclosed herein. In some examples, aspects of theoperations of 2120 may be performed by an SSB transmission manager 1135as described with reference to FIG. 11 .

FIG. 22 shows a flowchart illustrating a method 2200 that supportsconfiguring BWPs and SSBs in accordance with one or more aspects of thepresent disclosure. The operations of the method 2200 may be implementedby a network entity or its components as described herein. For example,the operations of the method 2200 may be performed by a network entityas described with reference to FIGS. 1 through 4 and 9 through 12 . Insome examples, a network entity may execute a set of instructions tocontrol the functional elements of the network entity to perform thedescribed functions. Additionally, or alternatively, the network entitymay perform aspects of the described functions using special-purposehardware.

At 2205, the method may include identifying an operating bandwidth forcommunications with a UE, where a first SSB is scheduled fortransmission in a first resource that is outside of the operatingbandwidth of the UE, and where the first SSB is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE. The operations of 2205may be performed in accordance with examples as disclosed herein. Insome examples, aspects of the operations of 2205 may be performed by aUE operating bandwidth manager 1125 as described with reference to FIG.11 .

At 2210, the method may include transmitting, based on identifying theoperating bandwidth for communications with the UE, control signalingthat schedules or enables a second SSB in a second resource of theoperating bandwidth of the UE. The operations of 2210 may be performedin accordance with examples as disclosed herein. In some examples,aspects of the operations of 2210 may be performed by an SSB schedulingmanager 1130 as described with reference to FIG. 11 .

At 2215, the method may include transmitting the control signaling via aDCI message that includes a field that enables monitoring at the UE forthe second SSB, the DCI message also including scheduling informationfor one or more shared channel transmissions. The operations of 2215 maybe performed in accordance with examples as disclosed herein. In someexamples, aspects of the operations of 2215 may be performed by a DCImanager 1150 as described with reference to FIG. 11 .

At 2220, the method may include transmitting the second SSB in thesecond resource. The operations of 2220 may be performed in accordancewith examples as disclosed herein. In some examples, aspects of theoperations of 2220 may be performed by an SSB transmission manager 1135as described with reference to FIG. 11 .

The following provides an overview of aspects of the present disclosure:

-   -   Aspect 1: A method for wireless communications at a UE,        comprising: receiving control signaling, in an operating        bandwidth of the UE, that schedules or enables a first SSB in a        first resource of the operating bandwidth of the UE, the first        SSB being different from a second SSB that is associated with        system information of a cell that operates across a radio        frequency bandwidth that includes the operating bandwidth of the        UE, wherein the second SSB is scheduled for receipt in a second        resource that is outside of the operating bandwidth of the UE;        and monitoring, while still operating in the operating bandwidth        of the UE, for the first SSB in the first resource based at        least in part on the control signaling.    -   Aspect 2: The method of aspect 1, further comprising: receiving        the first SSB without performing radio frequency retuning        between receiving the control signaling and monitoring for the        first SSB.    -   Aspect 3: The method of any of aspects 1 through 2, further        comprising: monitoring, prior to receiving the control        signaling, for a third SSB that is associated with system        information of the cell, wherein the third SSB is scheduled for        receipt in the second resource; and performing radio frequency        retuning from the second resource to the operating bandwidth of        the UE between monitoring for the third SSB and receiving the        control signaling.    -   Aspect 4: The method of any of aspects 1 through 3, wherein        receiving the control signaling comprises: receiving the control        signaling via a DCI message that includes one or more fields        that schedule the first SSB on the first resource.    -   Aspect 5: The method of any of aspects 1 through 4, wherein        receiving the control signaling comprises: receiving the control        signaling via a DCI message that includes a field that enables        the monitoring for the first SSB, the DCI message also including        scheduling information for one or more shared channel        transmissions.    -   Aspect 6: The method of aspect 5, further comprising: receiving        additional control signaling that schedules a frequency position        of the first SSB within the radio frequency bandwidth, the        additional control signaling received prior to the DCI message.    -   Aspect 7: The method of any of aspects 1 through 6, wherein        receiving the control signaling comprises: receiving the control        signaling via a DCI message that includes an indication of one        or more measurements associated with the first SSB.    -   Aspect 8: The method of any of aspects 1 through 7, wherein        receiving the control signaling comprises: receiving the control        signaling via a group common DCI message.    -   Aspect 9: The method of any of aspects 1 through 8, wherein        receiving the control signaling comprises: receiving the control        signaling via a MAC-CE that enables the monitoring for the first        SSB.    -   Aspect 10: The method of aspect 9, further comprising: receiving        second control signaling that schedules a set of semi-persistent        SSBs in a respective set of resources within the operating        bandwidth of the UE, the set of semi-persistent SSBs comprising        the first SSB, and the MAC-CE enabling the monitoring for the        set of semi-persistent SSBs.    -   Aspect 11: The method of aspect 10, further comprising:        receiving third control signaling deactivating the set of        semi-persistent SSBs; and monitoring for a third SSB in a third        resource outside of the operating bandwidth of the UE based at        least in part on the third control signaling, wherein the second        SSB and the third SSB are each part of a periodic set of SSBs in        a respective set of resources outside of the operating bandwidth        of the UE.    -   Aspect 12: The method of any of aspects 1 through 11, further        comprising: performing one of a radio resource management        procedure, a radio link monitoring procedure, or a bidirectional        forwarding detection procedure based at least in part on the        monitoring of the first SSB.    -   Aspect 13: The method of any of aspects 1 through 12, wherein        the second SSB comprises a cell-defining SSB and the first SSB        comprises a non-cell-defining SSB.    -   Aspect 14: The method of any of aspects 1 through 13, further        comprising: transmitting, to a network entity, a first control        message indicating that the UE is entering a reduced capability        mode; and receiving, from the network entity, a second control        message configuring the operating bandwidth of the UE based at        least in part on the first control message.    -   Aspect 15: A method for wireless communications at a network        entity, comprising: identifying an operating bandwidth for        communications with a UE, wherein a first SSB is scheduled for        transmission in a first resource that is outside of the        operating bandwidth of the UE, and wherein the first SSB is        associated with system information of a cell that operates        across a radio frequency bandwidth that includes the operating        bandwidth of the UE; transmitting, based at least in part on        identifying the operating bandwidth for communications with the        UE, control signaling that schedules or enables a second SSB in        a second resource of the operating bandwidth of the UE; and        transmitting the second SSB in the second resource.    -   Aspect 16: The method of aspect 15, further comprising:        identifying that a latency target associated with a data        transmission for the UE exceeds a threshold, wherein        transmitting the control signaling is based at least in part on        the identifying.    -   Aspect 17: The method of any of aspects 15 through 16, further        comprising: identifying that a payload size associated with a        data transmission for the UE exceeds a threshold, wherein        transmitting the control signaling is based at least in part on        the identifying.    -   Aspect 18: The method of any of aspects 15 through 17, wherein        transmitting the control signaling comprises: transmitting the        control signaling via a DCI message that includes one or more        fields that schedule the second SSB on the second resource.    -   Aspect 19: The method of any of aspects 15 through 18, wherein        transmitting the control signaling comprises: transmitting the        control signaling via a DCI message that includes a field that        enables monitoring at the UE for the second SSB, the DCI message        also including scheduling information for one or more shared        channel transmissions.    -   Aspect 20: The method of aspect 19, further comprising:        transmitting additional control signaling that schedules a        frequency position of the second SSB within the radio frequency        bandwidth, the additional control signaling received prior to        the DCI message.    -   Aspect 21: The method of any of aspects 15 through 20, wherein        transmitting the control signaling comprises: transmitting the        control signaling via a DCI message that includes an indication        of one or more measurements associated with the second SSB.    -   Aspect 22: The method of any of aspects 15 through 21, wherein        transmitting the control signaling comprises: transmitting the        control signaling via a group common DCI message.    -   Aspect 23: The method of any of aspects 15 through 22, wherein        transmitting the control signaling comprises: transmitting the        control signaling via a MAC-CE that enables monitoring at the UE        for the second SSB.    -   Aspect 24: The method of aspect 23, further comprising:        transmitting second control signaling that schedules a set of        semi-persistent SSBs in a respective set of resources within the        operating bandwidth of the UE, the set of semi-persistent SSBs        comprising the second SSB, and the MAC-CE enabling monitoring at        the UE for the set of semi-persistent SSBs.    -   Aspect 25: The method of aspect 24, further comprising:        transmitting third control signaling deactivating the set of        semi-persistent SSBs; and transmitting a third SSB in a third        resource outside of the operating bandwidth of the UE based at        least in part on the third control signaling, wherein the second        SSB and the third SSB are each part of a periodic set of SSBs in        a respective set of resources outside of the operating bandwidth        of the UE.    -   Aspect 26: The method of any of aspects 15 through 25, wherein        the first SSB comprises a cell-defining SSB and the second SSB        comprises a non-cell-defining SSB.    -   Aspect 27: The method of any of aspects 15 through 26, further        comprising: receiving, from the UE, a first control message        indicating that the UE is entering a reduced capability mode;        and transmitting, to the UE, a second control message        configuring the operating bandwidth of the UE based at least in        part on the first control message.    -   Aspect 28: An apparatus for wireless communications at a UE,        comprising at least one processor; and memory coupled with the        at least one processor, the memory storing instructions        executable by the at least one processor to cause the UE to        perform a method of any of aspects 1 through 14.    -   Aspect 29: An apparatus for wireless communications at a UE,        comprising at least one means for performing a method of any of        aspects 1 through 14.    -   Aspect 30: A non-transitory computer-readable medium storing        code for wireless communications at a UE, the code comprising        instructions executable by at least one processor to perform a        method of any of aspects 1 through 14.    -   Aspect 31: An apparatus for wireless communications at a network        entity, comprising at least one processor; and memory coupled        with the at least one processor, the memory storing instructions        executable by the at least one processor to cause the network        entity to perform a method of any of aspects 15 through 27.    -   Aspect 32: An apparatus for wireless communications at a network        entity, comprising at least one means for performing a method of        any of aspects 15 through 27.    -   Aspect 33: A non-transitory computer-readable medium storing        code for wireless communications at a network entity, the code        comprising instructions executable by at least one processor to        perform a method of any of aspects 15 through 27.

It should be noted that the methods described herein describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may bedescribed for purposes of example, and LTE, LTE-A, LTE-A Pro, or NRterminology may be used in much of the description, the techniquesdescribed herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NRnetworks. For example, the described techniques may be applicable tovarious other wireless communications systems such as Ultra MobileBroadband (UMB), Institute of Electrical and Electronics Engineers(IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, aswell as other systems and radio technologies including future systemsand radio technologies, not explicitly mentioned herein.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, a GPU, an ASIC, a CPU, an FPGA orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general-purpose processor maybe a microprocessor, but in the alternative, the processor may be anyprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices (e.g., acombination of a DSP and a microprocessor, multiple microprocessors, oneor more microprocessors in conjunction with a DSP core, or any othersuch configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, or any combination thereof. Software shall beconstrued broadly to mean instructions, instruction sets, code, codesegments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures, orfunctions, whether referred to as software, firmware, middleware,microcode, hardware description language, or otherwise. If implementedin software executed by a processor, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein may be implemented usingsoftware executed by a processor, hardware, hardwiring, or combinationsof any of these. Features implementing functions may also be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that may beaccessed by a general-purpose or special-purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media mayinclude RAM, ROM, electrically erasable programmable ROM (EEPROM), flashmemory, phase change memory, compact disk (CD) ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother non-transitory medium that may be used to carry or store desiredprogram code means in the form of instructions or data structures andthat may be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of computer-readable medium. Disk and disc,as used herein, include CD, laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an example step that is described as “based on condition A”may be based on both a condition A and a condition B without departingfrom the scope of the present disclosure. In other words, as usedherein, the phrase “based on” shall be construed in the same manner asthe phrase “based at least in part on.” As used herein, the term“and/or,” when used in a list of two or more items, means that any oneof the listed items can be employed by itself, or any combination of twoor more of the listed items can be employed. For example, if acomposition is described as containing components A, B, and/or C, thecomposition can contain A alone; B alone; C alone; A and B incombination; A and C in combination; B and C in combination; or A, B,and C in combination.

The term “determine” or “determining” encompasses a variety of actionsand, therefore, “determining” can include calculating, computing,processing, deriving, investigating, looking up (such as via looking upin a table, a database or another data structure), ascertaining and thelike. Also, “determining” can include receiving (such as receivinginformation), accessing (such as accessing data in a memory) and thelike. Also, “determining” can include resolving, obtaining, selecting,choosing, establishing and other such similar actions.

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “example” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, known structures and devices are shown inblock diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person having ordinaryskill in the art to make or use the disclosure. Various modifications tothe disclosure will be apparent to a person having ordinary skill in theart, and the generic principles defined herein may be applied to othervariations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described hereinbut is to be accorded the broadest scope consistent with the principlesand novel features disclosed herein.

What is claimed is:
 1. A method for wireless communications at a userequipment (UE), comprising: receiving control signaling, in an operatingbandwidth of the UE, that schedules or enables a first synchronizationsignal block in a first resource of the operating bandwidth of the UE,the first synchronization signal block being different from a secondsynchronization signal block that is associated with system informationof a cell that operates across a radio frequency bandwidth that includesthe operating bandwidth of the UE, wherein the second synchronizationsignal block is scheduled for receipt in a second resource that isoutside of the operating bandwidth of the UE; and monitoring, whilestill operating in the operating bandwidth of the UE, for the firstsynchronization signal block in the first resource based at least inpart on the control signaling.
 2. The method of claim 1, furthercomprising: receiving the first synchronization signal block withoutperforming radio frequency retuning between receiving the controlsignaling and monitoring for the first synchronization signal block. 3.The method of claim 1, further comprising: monitoring, prior toreceiving the control signaling, for a third synchronization signalblock that is associated with system information of the cell, whereinthe third synchronization signal block is scheduled for receipt in thesecond resource; and performing radio frequency retuning from the secondresource to the operating bandwidth of the UE between monitoring for thethird synchronization signal block and receiving the control signaling.4. The method of claim 1, wherein receiving the control signalingcomprises: receiving the control signaling via a downlink controlinformation message that includes one or more fields that schedule thefirst synchronization signal block on the first resource.
 5. The methodof claim 1, wherein receiving the control signaling comprises: receivingthe control signaling via a downlink control information message thatincludes a field that enables the monitoring for the firstsynchronization signal block, the downlink control information messagealso including scheduling information for one or more shared channeltransmissions.
 6. The method of claim 5, further comprising: receivingadditional control signaling that schedules a frequency position of thefirst synchronization signal block within the radio frequency bandwidth,the additional control signaling received prior to the downlink controlinformation message.
 7. The method of claim 1, wherein receiving thecontrol signaling comprises: receiving the control signaling via adownlink control information message that includes an indication of oneor more measurements associated with the first synchronization signalblock.
 8. The method of claim 1, wherein receiving the control signalingcomprises: receiving the control signaling via a group common downlinkcontrol information message.
 9. The method of claim 1, wherein receivingthe control signaling comprises: receiving the control signaling via amedium access control (MAC) control element (CE) that enables themonitoring for the first synchronization signal block.
 10. The method ofclaim 9, further comprising: receiving second control signaling thatschedules a set of semi-persistent synchronization signal blocks in arespective set of resources within the operating bandwidth of the UE,the set of semi-persistent synchronization signal blocks comprising thefirst synchronization signal block, and the MAC-CE enabling themonitoring for the set of semi-persistent synchronization signal blocks.11. The method of claim 10, further comprising: receiving third controlsignaling deactivating the set of semi-persistent synchronization signalblocks; and monitoring for a third synchronization signal block in athird resource outside of the operating bandwidth of the UE based atleast in part on the third control signaling, wherein the secondsynchronization signal block and the third synchronization signal blockare each part of a periodic set of synchronization signal blocks in arespective set of resources outside of the operating bandwidth of theUE.
 12. The method of claim 1, further comprising: performing one of aradio resource management procedure, a radio link monitoring procedure,or a bidirectional forwarding detection procedure based at least in parton the monitoring of the first synchronization signal block.
 13. Themethod of claim 1, wherein the second synchronization signal blockcomprises a cell-defining synchronization signal block and the firstsynchronization signal block comprises a non-cell-definingsynchronization signal block.
 14. The method of claim 1, furthercomprising: transmitting, to a network entity, a first control messageindicating that the UE is entering a reduced capability mode; andreceiving, from the network entity, a second control message configuringthe operating bandwidth of the UE based at least in part on the firstcontrol message.
 15. A method for wireless communications at a networkentity, comprising: identifying an operating bandwidth forcommunications with a user equipment (UE), wherein a firstsynchronization signal block is scheduled for transmission in a firstresource that is outside of the operating bandwidth of the UE, andwherein the first synchronization signal block is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE; transmitting, based atleast in part on identifying the operating bandwidth for communicationswith the UE, control signaling that schedules or enables a secondsynchronization signal block in a second resource of the operatingbandwidth of the UE; and transmitting the second synchronization signalblock in the second resource.
 16. The method of claim 15, furthercomprising: identifying that a latency target associated with a datatransmission for the UE exceeds a threshold, wherein transmitting thecontrol signaling is based at least in part on the identifying.
 17. Themethod of claim 15, further comprising: identifying that a payload sizeassociated with a data transmission for the UE exceeds a threshold,wherein transmitting the control signaling is based at least in part onthe identifying.
 18. The method of claim 15, wherein transmitting thecontrol signaling comprises: transmitting the control signaling via adownlink control information message that includes one or more fieldsthat schedule the second synchronization signal block on the secondresource.
 19. The method of claim 15, wherein transmitting the controlsignaling comprises: transmitting the control signaling via a downlinkcontrol information message that includes a field that enablesmonitoring at the UE for the second synchronization signal block, thedownlink control information message also including schedulinginformation for one or more shared channel transmissions.
 20. The methodof claim 19, further comprising: transmitting additional controlsignaling that schedules a frequency position of the secondsynchronization signal block within the radio frequency bandwidth, theadditional control signaling received prior to the downlink controlinformation message.
 21. The method of claim 15, wherein transmittingthe control signaling comprises: transmitting the control signaling viaa downlink control information message that includes an indication ofone or more measurements associated with the second synchronizationsignal block.
 22. The method of claim 15, wherein transmitting thecontrol signaling comprises: transmitting the control signaling via agroup common downlink control information message.
 23. The method ofclaim 15, wherein transmitting the control signaling comprises:transmitting the control signaling via a medium access control (MAC)control element (CE) that enables monitoring at the UE for the secondsynchronization signal block.
 24. The method of claim 23, furthercomprising: transmitting second control signaling that schedules a setof semi-persistent synchronization signal blocks in a respective set ofresources within the operating bandwidth of the UE, the set ofsemi-persistent synchronization signal blocks comprising the secondsynchronization signal block, and the MAC-CE enabling monitoring at theUE for the set of semi-persistent synchronization signal blocks.
 25. Themethod of claim 24, further comprising: transmitting third controlsignaling deactivating the set of semi-persistent synchronization signalblocks; and transmitting a third synchronization signal block in a thirdresource outside of the operating bandwidth of the UE based at least inpart on the third control signaling, wherein the second synchronizationsignal block and the third synchronization signal block are each part ofa periodic set of synchronization signal blocks in a respective set ofresources outside of the operating bandwidth of the UE.
 26. The methodof claim 15, wherein the first synchronization signal block comprises acell-defining synchronization signal block and the secondsynchronization signal block comprises a non-cell-definingsynchronization signal block.
 27. The method of claim 15, furthercomprising: receiving, from the UE, a first control message indicatingthat the UE is entering a reduced capability mode; and transmitting, tothe UE, a second control message configuring the operating bandwidth ofthe UE based at least in part on the first control message.
 28. Anapparatus for wireless communications at a user equipment (UE),comprising: at least one processor; and memory coupled with the at leastone processor, the memory storing instruction executable by the at leastone processor to cause the UE to: receive control signaling, in anoperating bandwidth of the UE, that schedules or enables a firstsynchronization signal block in a first resource of the operatingbandwidth of the UE, the first synchronization signal block beingdifferent from a second synchronization signal block that is associatedwith system information of a cell that operates across a radio frequencybandwidth that includes the operating bandwidth of the UE, wherein thesecond synchronization signal block is scheduled for receipt in a secondresource that is outside of the operating bandwidth of the UE; andmonitor, while still operating in the operating bandwidth of the UE, forthe first synchronization signal block in the first resource based atleast in part on the control signaling.
 29. The apparatus of claim 28,wherein the instructions are further executable by the at least oneprocessor to cause the UE to: receive the first synchronization signalblock without performing radio frequency retuning between receiving thecontrol signaling and monitoring for the first synchronization signalblock.
 30. An apparatus for wireless communications at a network entity,comprising: at least one processor; and memory coupled with the at leastone processor, the memory storing instruction executable by the at leastone processor to cause the network entity to: identify an operatingbandwidth for communications with a user equipment (UE), wherein a firstsynchronization signal block is scheduled for transmission in a firstresource that is outside of the operating bandwidth of the UE, andwherein the first synchronization signal block is associated with systeminformation of a cell that operates across a radio frequency bandwidththat includes the operating bandwidth of the UE; transmit, based atleast in part on identifying the operating bandwidth for communicationswith the UE, control signaling that schedules or enables a secondsynchronization signal block in a second resource of the operatingbandwidth of the UE; and transmit the second synchronization signalblock in the second resource.